fix for filenames with spaces on windows

[reiner-dolp]

before this change, opening a path containing a space only opens an empty cmd prompt.

Only tested on Windows 10.

[Byron]

Thanks a lot, and sorry for the late reply.
Even though I have no doubts this works for you, I wonder if you could verify it to work on the other cases too, or on other windows versions.

[reiner-dolp]

the windows start command has a unfortunate design where it takes an optional title as first argument. I think the problem is that a call start arg without an optional title is interpreted as title="" command=arg for paths without spaces and as title=arg cmd="" for paths with spaces. This patch explicitly sets the title to "" to resolve the issue.

German help output:

C:\Users\Reiner>start /?
Startet ein eigenes Fenster, um ein bestimmtes Programm oder einen Befehl
auszuführen.

START ["Titel"] [/D Pfad] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/LOW | /NORMAL | /HIGH | /REALTIME] | /ABOVENORMAL | /BELOWNORMAL]
      [/NODE <NUMA-Knoten>] [/AFFINITY <Hex.-Affinitätsmaske>] [/WAIT] [/B]
      [Befehl/Programm]
      [Parameter]

A popular javscript library employs the same fix.

[Byron]

Thanks a bunch for the explanation!
This also means that cmd (or start) parse their arguments themselves and split across spaces, as Rust does not use a shell when spawning programs which would be prone to spaces in arguments otherwise.
It’s odd, for sure 😁.

[Byron]

I will see to get a new release out soon