Skip to content
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

Surprising quoting behavior in wsl command from Windows #11635

Closed
1 of 2 tasks
Noratrieb opened this issue May 31, 2024 · 2 comments
Closed
1 of 2 tasks

Surprising quoting behavior in wsl command from Windows #11635

Noratrieb opened this issue May 31, 2024 · 2 comments

Comments

@Noratrieb
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.4412]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1

Distro Version

Ubuntu 22.04, Ubuntu 24.04

Other Software

No response

Repro Steps

In PowerShell:

$ wsl echo "a\a"
aa
$ wsl echo "a \a"
a\a

Expected Behavior

I expected consistent behavior wrt the escaping of the backslash. My user case was passing a Windows path to WSL (to be converted with wslpath and then used) and when the path didn't contain spaces, it didn't work correctly, and if it did contain spaces, it worked.

Actual Behavior

Consistent behavior, where the backslash is shown both times or never.

Diagnostic Logs

I wrote a quick Rust program to dump argv and set that as my shell.

In the first case, the shell's argv was [/path/to/executable, -c, echo a\a].
In the second case, it was [/path/to/executable, -c, echo "a \a"].
So it looks like wsl conditionally wraps the argument in quotes when it would be split by bash.

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant