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.
From Remote WSL environment. Cannot open folder with spaces.
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.
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:
folderWithoutSpacesandfolder with spaces. I'm trying to open these in Windows Terminal.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.