[Gretl-devel] Re: shell escape on Windows: issue with quited path strings
Am 22.06.2021 um 23:55 schrieb Allin Cottrell:
On Tue, 22 Jun 2021, Sven Schreiber wrote:
> However, when I enclose everything in quotes (to be more portable, in
> case the user name does contain a space) then it fails, i.e. the
> expected output files are not created! Like this:
>
> ! "C:\mypath\some.exe" "C:\morepath\input.csv" >
"C\morepath\output.txt"
[note that some colons were "eaten" here
along the way back-and-forth on
the mailing list, the line above is not what I had posted, it's always
C-colon-backslash...]
>
> I find this really puzzling - is something going wrong on the way from
> gretl to the Windows shell, or am I simply missing something?
It might be helpful to know what you're actually trying to do here, in
particular what the "some.exe" is.
Fair enough, but instead let me give you a more complete self-contained
example:
! "c:\Programme\LyX 2.3\Python\python.exe" c:\users\public\uhu.py >
c:\users\public\testout\haha.txt
The file uhu.py just contains the statement print(5), and the testout
directory exists alright. This call from a gretl script works OK as
written above, where only the path to python.exe is quoted. As described
before, it fails if I enclose the other paths in quotes. (But both work
directly in Windows's cmd prompt.)
thanks
sven