On Mon Feb 9 01:59:00 2026 +0000, eric pouech wrote:
replying to myself I think the (at least the first one \<g\>) issue lies in cmd's arg parsing when handling the builtin START command using your test with /d "foo\\" cmd.exe, and looking at argv in start.exe, last argv is `"foo\" cmd.exe` which is not what's expected (we want two args instead of one) and looking at arg parsing result in builtin start command in cmd.exe, we do get `"foo\" foo.exe` as a single arg so another approach could be to fix the arg parsing in cmd.exe (and likely afterwards, the strings passed to external start.exe shall be properly escaped - as shown by trying from cmd.exe `start "foo\" notepad.exe` - doesn't start notepad \<g\>) I think I understand what you mean. I will copy the `WCMD_parameter` function and use it to parse the command line obtained from `GetCommandLineW`, then reconstruct the `argv` for the `start` command.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10008#note_129119