-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-133545: Also quote arguments containing &<>^|
on Windows
#134544
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
base: main
Are you sure you want to change the base?
Conversation
:&<>^|
on Windows&<>^|
on Windows
looping in @zooba for windows specific experience as it behaves differently than others perhaps do. could this break real use cases that we just lack coverage for when launching processes? |
Those characters only need to be quoted when launching We decided a while back that explicitly launching I'm pretty sure this change as it stands will affect all executables. We should only check for those extra characters in user-provided arguments when Perhaps there's a middle ground somewhere, but I'm not sure where it is. But I'm pretty sure this PR isn't it - we definitely need to know about the caller's intent before modifying their arguments here. |
I agree that the special characters should not be quoted when Also I believe that this test needs to have |
I think the main issue is that currently it is either quoting/escaping too much or too little. I would expect at least one (preferably two) of these test cases would pass, but they can't because redirections aren't quoted automatically and if we try to quote them then those quotes are escaped. This happens regardless if
|
In addition to space, tab, and empty string, quote arguments containing
&<>^|
on Windows.Resolves #133545.