http://bugs.winehq.org/show_bug.cgi?id=21227
--- Comment #15 from Eric Pouech eric.pouech@gmail.com --- (In reply to Vijay Kamuju from comment #13)
dir > blah > bad command always creates the empty file blah, but on windows it does not create it.
Tested on wine 9.12 and windows 10
(In reply to lizhenbo from comment #12)
This is still an issue in wine 9.4, and hear is a simplified real world case
@if not defined _echo @echo off set _C=-c "import sys; sys.stdout.write(sys.executable)" (py -3 %_C% || py -2 %_C% || python3 %_C% || python2 %_C% || python %_C%) > pythonlocation.txt 2> NUL set _C= set /p PYTHON=pythonlocation.txt if NOT DEFINED PYTHON ( echo %__MsgPrefix%Error: Could not find a Python installation. exit /b 1 ) echo Success
not very clear to me how this relates to previous discussion (which were about extraneous white space on echoing commands)
IMO, the script should be: set /p PYTHON=<pythonlocation.txt (mind the missing < after the =)
but this fails on current Wine (10.16) unless written as set /p PYTHON=< pythonlocation.txt (mind the extra space after <)
which looks like a lexer/parser issue; if all the assumptions just above are correct, please file a different bug