This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 62
args to custom run command not working correctly on windows (spaces?) #224
Comments
as a workaround I was able to get it working by changing my configuration to include quotes around the path:
so maybe vscode-rust should quote all arguments automatically? I don't know if this would cause problems elsewhere though. |
I don't really know the details that well, but it doesn't look like exactly the same issue? it seems the nodeJS bug is about when the command has a space, but I don't think the command here has a space. edit: by "command", I mean "executable path" |
I suppose NodeJS behave the same disregarding whether it is an executable path or an argument |
I do actually think it is easy to avoid, so I am going to open a PR to fix this. |
I was wrong. It is not easy) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version of VSCode: 1.11.2
Version of the extension: 0.3.14
OS: Windows 10
Description:
I have a custom run configuration like this:
Since the latest update, I can't use it any more. It seems that the command is now being run in PowerShell, and my guess is that it's not escaping spaces correctly (e.g. in the "Google Drive" path).
Output of the "Rust logging" channel:
The text was updated successfully, but these errors were encountered: