This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin manpages clobbered
- From: Warren Young <warren at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 10 May 2013 11:13:12 -0600
- Subject: Re: Cygwin manpages clobbered
- References: <5F8AAC04F9616747BC4CC0E803D5907D0AF787B3 at MLBXv04 dot nih dot gov> <518C55BD dot 7020807 at etr-usa dot com> <20130510041245 dot GA3019 at ednor dot casa dot cgf dot cx> <518CC275 dot 2060207 at etr-usa dot com> <20130510142904 dot GA6201 at ednor dot casa dot cgf dot cx> <20130510143137 dot GA1135 at ednor dot casa dot cgf dot cx>
On 5/10/2013 08:31, Christopher Faylor wrote:
I don't know what Corinna's return has to do with this.
The open question is whether we're going to switch all the DOCTOOL tags
and *.sgml in winsup/cygwin to Doxygen, or keep it as DocBook but move
it all to winsup/doc.
I can do it either way. I just think Doxygen gets us more with less
effort. (DocBook is still the way to go for prose-heavy documents like
the Cygwin FAQ and user manual.)
One Doxygen advantage I haven't mentioned yet: the most basic sort of
Doxygen comments on the POSIX interfaces would get Cygwin a set of basic
man2 pages for cheap.
I don't propose to try and replace the POSIX docs or the Linux man
pages, but at least we could give vi users pressing K on a syscall a
parameter list and return value description.
If you're making the call now, nixing the Doxygen conversion idea, I can
start moving the docs out of the source subdirectories.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple