Handle windows paths in all usage of shellwords parsing #686
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This centralises our use of shellword parsing (e.g parsing something like
C:\Windows\System32\CMD.exe /S /C "bash.exe ./upload.sh"
into it's respective tokens).It turns out the Windows is ok with paths with forward slashes, even for UNC paths, so this just rolls with that.
It also sneakily rolls back #683 in favour of just converting the path to the binary to one that uses backslashes.