https://bugs.winehq.org/show_bug.cgi?id=44132
Jason Edmeades us@edmeades.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |us@edmeades.me.uk
--- Comment #1 from Jason Edmeades us@edmeades.me.uk --- This doesnt work on windows either, and I believe needs to be resolved invalid.
(The root cause of your problem based on the description of the mkdir issue is probably bug#40694 (just attached a patch) in that the "C:<space>&" fails)
(Windows 10:)
C:\luajit>luajit -e "print(os.execute("\"C:\luajit\luajit\" -e \"print(1)\""))" 'C:\luajit\luajit" -e "print' is not recognized as an internal or external command, operable program or batch file. nil exit 1
In effect this launches: cmd /c "C:\luajit\luajit.exe" -e "print(1)"
Windows states (see cmd.exe /?):
If /C or /K is specified, then the remainder of the command line after the switch is processed as a command line, where the following logic is used to process quote (") characters:
1. If all of the following conditions are met, then quote characters on the command line are preserved:
- no /S switch - exactly two quote characters - no special characters between the two quote characters, where special is one of: &<>()@^| - there are one or more whitespace characters between the two quote characters - the string between the two quote characters is the name of an executable file.
2. Otherwise, old behavior is to see if the first character is a quote character and if so, strip the leading character and remove the last quote character on the command line, preserving any text after the last quote character.
You hit condition 2, so the first and last quote are removed, and it tries to run the rest as a single command, which obviously fails.