Am 24.06.2021 um 02:38 schrieb Allin Cottrell:
Now I see that this sort of thing does not work on Windows. My test
example was a trivial program, printarg.exe, which prints out its first
argument. My "shell" line in gretl read thus:
! "c:\users\cottrell\printarg.exe" "foo" >
Gretl takes this input and turns it into the following request to the
operating system (with trailing backslash indicating line continuation):
Is this backslash inserted by you for the sake of the email message
here, or is it actually added by gretl before passing it to cmd.exe?
"foo" > "c:\users\cottrell\print.out"
which looks OK to me. But Windows comes back with:
C:\WINDOWS\system32\cmd.exe /c "c:\users\cottrell\printarg.exe" \
'c:\users\cottrell\printarg.exe" "foo' is not recognized as an
or external command, operable program or batch file.
Apart from the 1>, I'm noticing that the leading and trailing double
quote signs do not appear in Windows's last sentence. (Starts with 'c,
That is, the first two double-quoted elements of the command line
been run together by the OS in a way that's not easy to understand.
If you'd like to contribute to getting this working on Windows, please
research the required cmd.exe syntax and let me know what we need to do.
Will do, but I think I need your answer on the question above.