-
-
Couldn't load subscription status.
- Fork 5.7k
fix command literals with trailing backslashes #41041
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
Conversation
|
Bumping this again. |
`` `\\` `` currently throws an error because it is parsed as `@cmd "\\"` due to escaping in the parser and `shell_parse` therefore thinks it's a dangling backslash.
407f798 to
0662f62
Compare
|
I tried finishing this PR, but Pkg currently relies on the existing behavior in one place: The trouble being that |
Similar to how `escape_raw_string` enabled users to reverse the transform done by string literals, this enables users to reverse the transform done by cmd literals by specifying an argument of a '\`'. Refs #41041
Similar to how `escape_raw_string` enabled users to reverse the transform done by string literals, this enables users to reverse the transform done by cmd literals by specifying an argument of a '\`'. Refs #41041 Co-authored-by: Simeon Schaub <[email protected]>
|
Superseded by #52001 |
`\\`currently throws an error because it is parsed as@cmd "\\"due to escaping in the parser and
shell_parsetherefore thinks it's adangling backslash.