Csaba Halász wrote: > On Jan 28, 2008 10:32 AM, Stuart Buchanan <[EMAIL PROTECTED]> wrote: > >> --- Curtis Olson wrote: >> >>> On Jan 27, 2008 3:51 AM, Frederic Bouvier wrote: >>> >>> >>>> Stuart Buchanan a écrit : >>>> >>>>> Hi All, >>>>> >>>>> One of the frustrations of using Windows for development is the lack of >>>>> >>>> a >>>> >>>>> sensible way to re-direct stderr to a file. >>>>> > > Isn't the cmd.exe the normal shell? > > http://technet.microsoft.com/en-us/library/bb490982.aspx > > >From this it seems to me windows supports similar (if not same!) > syntax for redirection. > > Csaba is correct. Pretty sure it'll even work on Win9x (but who'd want to ;)
Examples: 'fgfs [...your options...] 1>sout.txt 2>serr.txt' will send stdout to 'sout.txt' and stderr to 'serr.txt' 'fgfs [...your options...] >>output.txt 2>&1' will send both stdout and stderr to 'output.txt' Probably a more practical problem is that most Windows FlightGear users will be launching fgfs from fgrun and not the command line. The good news is that if you start *fgrun* from the command line with the redirection, you'll actually be redirecting fgfs's output. If a Windows user is deathly afraid of the command line, you could walk them through changing the fgrun shortcut (icon) properties to include the redirection (right-click the icon, choose 'Properties', edit the 'Target' field to include the new command line options). ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
