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

Cannot open Windows Terminal from WSL when the folder name has spaces #28

Closed
moxwel opened this issue Mar 25, 2021 · 0 comments · Fixed by #29
Closed

Cannot open Windows Terminal from WSL when the folder name has spaces #28

moxwel opened this issue Mar 25, 2021 · 0 comments · Fixed by #29
Labels
bug Something isn't working

Comments

@moxwel
Copy link
Contributor

moxwel commented Mar 25, 2021

I'm doing testing, and found that: if there is a folder (or folders) in the "Open in Windows Terminal" path with spaces in their names, Windows Terminal doesn't open.

Here I have 2 folders: folderWithoutSpaces and folder with spaces. I'm trying to open these in Windows Terminal.

From Windows environment. No problem.
windows

From Remote WSL environment. Cannot open folder with spaces.
wsl

Apparently this only occur with a Remote WSL environment in VSCode.

This extension is just what I was looking for, but I have some projects on folders where their names has spaces, and they gave me these errors because I use WSL.

@Tyriar Tyriar added the bug Something isn't working label May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants