This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: XWin -help behavior
- From: "Harold Hunt" <huntharo at msu dot edu>
- To: "Thomas Chadwick" <j_tetazoo at hotmail dot com>, <cygwin-xfree at cygwin dot com>
- Date: Mon, 29 Apr 2002 10:40:31 -0400
- Subject: RE: XWin -help behavior
Thomas,
Yes, that's a great idea. There is one problem though. We redirect the
ErrorF function (which prints out all messages, including the --help
message) before we know that a --help parameter is coming down the line.
When the --help is processed is calls a UseMsg function that then calls a
module-UseMsg function for each part of the XFree86 server. By the time
that ddxUseMsg (that's the hardware layer's (our's) UseMsg function) gets
called we have already printed out 90% of the help text, so there is very
little point in redirecting our portion of the help message to STDERR.
The solution lies in creating an overly-complicated ErrorF system that
buffers the output until we have processed all command-line parameters. I
don't have time to do that, do you?
Harold
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Thomas Chadwick
> Sent: Monday, April 29, 2002 10:31 AM
> To: cygwin-xfree@cygwin.com
> Subject: XWin -help behavior
>
>
> I just noticed today that if I run "XWin -help", I don't see
> anything at the
> command-line. I have to go look in /tmp/XWin.log to see the results.
>
> Would it make send to print this information to STERR instead of the log
> file?
>
>
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
>