Dragging and dropping a file into a WSL terminal will use the incorrect '\' separator

[alphagocc]

• VSCode Version: 1.37.0
• OS Version: 10.0.18632

Steps to Reproduce:

Drag a file to the WSL Shell

File path separator is '\' not '/'

Does this issue occur when all extensions are disabled?: Yes
（But in fact I have to enable Remote WSL extensions

[Tyriar]

Note to self: For files dragged in via OS they should be resolved in window, dragged in via file explorer should be resolved in ext host. One complication here is for WSL where we need to run wslpath for files dragged from explorer, this might need better WSL terminal detection and marking terminal instances with additional information.

[eamodio]

For verification:

Setup: Windows 10

1. Open a PowerShell terminal
2. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
3. Open a PowerShell Core terminal
4. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
5. Open a Command Prompt terminal
6. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
7. Open a Git Bash terminal
8. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes /
9. Open a WSL terminal
10. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes /, and that the path is translated into a WSL path (e.g. /mnt/*)

---

1. Open a PowerShell or Command Prompt terminal
2. Run powershell.exe
3. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
4. Run pwsh.exe (PowerShell Core)
5. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
6. Run cmd.exe
7. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes \
8. Run bash.exe (from Git)
9. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes /
10. Run wsl.exe
11. Ensure that when dragging a file from the desktop or from the vscode explorer the path has the correct slashes /, and that the path is translated into a WSL path (e.g. /mnt/*)

[alexr00]

Dragging any file into a wsl integrated terminal doesn't produce a path for me.

[alexr00]

When I start with a powershell integrated terminal, then run git bash.exe, dragging a file from the desktop into the terminal produces the wrong slashes. From VS Code file explorer it's ok. When the integrated terminal starts as git bash it's also ok.

[alexr00]

Finally, when I start with a powershell integrated terminal, then run wsl.exe, dragging a file from the VS Code explorer doesn't produce a path. Dragging a file from the desktop produce a Windows path.

[eamodio]

@alexr00 are you on WSL1? Also what version of Windows?

[alexr00]

Yes, I"m on WSL 1. Windows version 1901, build 18363.418. Default distro is Alpine.

[CM000n]

I also have this behavior. When I drag and drop a file from a WSL filelist into the WSL bash, VS code creates a path specification that uses \ instead of /.

It cannot find the folder/file under the path thus generated by VS Code:

If I manually replace the \ with / in the path specification, it no longer has any problems finding the file:

I use Ubuntu-20.04 as WSL 2 and VS Code 1.57.0

[melink14]

I also noticed the reverse being true, clicking file names in the WSL terminal will trigger a search with all the slashes reversed. Might be unrelated but including in case it's a clue to the larger problem.

[CM000n]

Are there any news on this?
For me, unfortunately, this is one of the most annoying behaviors when developping with VSCode under a WSL