-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PowerShell quoting #33
Comments
OK, so I guess the solution is to:
This should cover all the quoting cases for PowerShell. Of course, then the dry-run output won't work in Command Prompt anymore... but I'm not sure we can have it both ways. Not unless there is a way to check the type of the attached console. |
Probably will be sufficient to check an environment variable like |
In my hands (I personally think it's okay to not support the cmd.exe case here.) |
The
--dry-run
output on Windows works in Command Prompt, but not PowerShell, because PowerShell gets weird about unquoted arguments with the dot (.) symbol. Should the Windows--dry-run
put double quotes around each argument?The text was updated successfully, but these errors were encountered: