[Gretl-users] Assorted little bugs

[Allin Cottrell]

On Mon, 30 Apr 2007, Sven Schreiber wrote:

> > This is completely untested -- but the snapshot I'm putting in 
> > place right now has a new -g or --debug command-line option for
> > gretlw32.exe.  This is intended to send stdout and stderr to a 
> > console window.
> > 
> 
> Well thanks, but it's not working... After typing "gretlw32.exe -g" (or
> --debug) nothing happens. (In contrast to "gretlw32.exe", which starts
> gretl alright, so it's not a path issue or something like that.)
> 
> However, it may be unnecessary anyway; I read somewhere that stdout and
> stderr for any Windows program can be redirected to text files when the
> programs are started like this (assuming proper write permissions):
> 
> 1) stdout:
> gretlw32.exe >gretlout.txt
> 
> 2) stderr:
> gretlw32.exe 2>gretlerrout.txt

Yes, that does seem to work.  I've had one more go at the 
"redirect stderr to console" code in the latest Windows snapshot, 
because it seems it might be useful to see the errors as they 
appear, but I won't persevere if it still doesn't work.

Allin.