Issue with Path Completion in Cmder and VSCode on Windows

[alvaronavega]

Hello, community!

I’m encountering a problem with using forward slashes / instead of backslashes \ for file paths in Cmder and Visual Studio Code (VSCode) on Windows.

Context

• Terminal: Cmder
• Code Editor: Visual Studio Code (VSCode)
• Issue: I would like to use forward slashes / instead of backslashes \ for file paths, but I’m having difficulty configuring this both in Cmder and VSCode. In Cmder, the Tab key still inserts backslashes, and in VSCode, forward slashes are not correctly recognized in some cases.

What I’ve Tried

1. Cmder:

   • I attempted to adjust settings to force the use of forward slashes, but couldn’t find an effective configuration.

2. VSCode:

   • I checked the integrated terminal and path settings, but I’m still having issues with the interpretation of forward slashes in file paths.

Questions

1. Is there a specific setting in Cmder that I can adjust to use forward slashes instead of backslashes in file paths?
2. How can I configure VSCode to accept and recognize forward slashes instead of backslashes in file paths?
3. Any recommendations or solutions you know of for dealing with this issue in both environments?

Thank you in advance for your help!

[DRSDavidSoft]

Can you please tell us which one of the shells you are using? If this is clink (the default shell in Cmder) then make sure that both VS Code and Cmder is using the same shell first.

If you made sure that both of them are in fact clink, then do clink info and post the results here. Please also read this issue and see if any of the available configurations works for your case:
#2947

Here is the relevant part of clink's configuration:
https://chrisant996.github.io/clink/clink.html#match_translate_slashes

Of course this is only relevant to path completion, I believe. You didn't specify what problem you had when you said "forward slashes are not correctly recognized in some cases". It's unclear and ambiguous. When you specified that "the Tab key still inserts backslashes" I believe you mean the problem is related to path completion, which I linked above.

If your problem is not related to clink, it may be related to the other shells such as PowerShell and bash, in which case the above configuration is not relevant.

[alvaronavega]

Thank you very much for the help! Sorry for the poorly formulated message, but my English is terrible. However, I used match.translate_slashes 2 and it solved my problem. Sorry for my lack of knowledge, but I was not familiar with Cmder and Clink yet.

[DRSDavidSoft]

No problem, we're happy that you find Cmder and especially Clink useful!

[ujjwalshriv3]

Thanks for such a useful information abt this