> One thing about the logfile: The usage message should not into > the logfile!
Yeah, I just ran into the same issue when I ran: XWin -help There was no output :) > And how can I switch off logging to a logfile? I like seeing the output > of Xwin. It's better for debugging and isolating problems. That's a tricky one. I admit that it would be great to be able to toggle between logged output and console output. However, there is an issue that stands in the way. The problem is that we have to make a choice between the X Server being a Windows executable or a DOS executable. DOS executables open that annoying DOS box that doesn't do anything if you are logging to a file. Windows executables don't open a DOS box in any circumstance, even when you want to output to the console. That gives us a dilemma because we can't have a Windows executable that allows console output, yet we don't want a DOS executable for when we are logging to a file. Unfortunately there does not appear to be an optimum solution. We can use the run.exe utility to prevent a DOS box when logging to file, rather than making XWin.exe a Windows executable, but that is kind of ugly and requires that the user be on his/her toes when switching from logged output to console output (they have to remember not to use run.exe when using console output). I don't know... I don't care. Fix it yourself to whatever degree you deem necessary (just don't take away my file logging option), then send the patches to [EMAIL PROTECTED] Just make sure that you come up with a comprehensive solution that addresses debugging, run time, file logging, console output, etc. There's a lot to think about, that's why the current solution sucks :) Harold
