Re: [Gretl-devel] "start gretlcli.exe" vs. simple "gretlcli.exe" (on Windows)
On Tue, 10 Jan 2017, Sven Schreiber wrote:
Hi,
allow me to open a new thread for the shell command launching stuff here.
I'm following Allin's advice to use "start gretlcli" to background the
gretlcli process on Windows. The problem I'm facing right now (with the
latest snapshot) is that when I do (in the Windows cmd.exe console):
gretlcli.exe -b hansltemp.inp > testy.out
I get a good testy.out file written. However, when I do:
start gretlcli.exe -b hansltemp.inp > testy.out
The testy.out file gets overwritten as expected, but it is empty (0 bytes). I
know this might be a Windows issue instead of a gretl issue, but perhaps
somebody has an idea about what's going on nevertheless.
That sounds like the same issue as using "launch" on Linux: output
redirection on the command line doesn't work in asynchronous use.
You'll have to use "outfile" to control where output goes.
(I've now experimented on Windows and what you describe is exactly
what happens when you use "start" from the cmd.exe prompt outside of
gretl: if you attempt redirection, the file pointed to by ">" ends up
empty.)
Allin