-
Notifications
You must be signed in to change notification settings - Fork 859
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
wsl --list in powershell script, many unexpected space characters #4180
Comments
Are you sure? Does your script parse the output if the string "( It's correct, just, well, unfortunate. You can probably get to where you want to be from Linux with:
From Powershell, I'm not qualified to repeat the Google hits. |
I can leave without this |
It is not a bug. It is powershell's by-design behavior. And unrelated to |
As mentioned in #4607, it is unexpected that WSL outputs multi-byte codepoints. I suspect this bug was closed too hastily. It's unclear if this even went through proper triage; it doesn't appear @therealkenc works at Microsoft... |
But I tried it now and it works correctly in all consoles :) |
I need to
wsl -l
in my dotfiles, but it doesn't behave correctly, when I use this command with pipe or redirection, output looks like this:I'm talking about these commands:
wsl -l | echo
wsl -l | sls ubuntu
wsl -l > file.txt
Does anybody have any idea how to workaround this problem?
The text was updated successfully, but these errors were encountered: