> > Several people have mentioned changes they would like to see in
> > cygport's documentation. I believe the stable APIs are all documented
> > now, but what more would you like to see in the docs?
>
> I'd like to see an explanation and an example or two of what cygclasses are
> for.
Also:
> Several people have mentioned changes they would like to see in
> cygport's documentation. I believe the stable APIs are all documented
> now, but what more would you like to see in the docs?
I'd like to see an explanation and an example or two of what cygclasses are for.
On Jun 13 16:53, Warren Young wrote:
> On 6/13/2013 13:50, Achim Gratz wrote:
> >
> >a tutorial or
> >similarly styled explanation of how to use cygport,
>
> That, or a recipe format, or a FAQ format. That is, one that starts
> with "how", rather than "what".
>
> >it would probably
> >help if th
On 6/13/2013 13:50, Achim Gratz wrote:
a tutorial or
similarly styled explanation of how to use cygport,
That, or a recipe format, or a FAQ format. That is, one that starts
with "how", rather than "what".
it would probably
help if the "manual" was called a "reference" to tone the expectat
Yaakov (Cygwin/X) writes:
> Several people have mentioned changes they would like to see in
> cygport's documentation. I believe the stable APIs are all documented
> now, but what more would you like to see in the docs?
I guess from my own (still growing) experience that a tutorial or
similarly s
Several people have mentioned changes they would like to see in
cygport's documentation. I believe the stable APIs are all documented
now, but what more would you like to see in the docs?
Yaakov
