-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Error: Failed to copy ConEmu.xml file to user-conemu.xml backup location! #1930
Comments
No, I'm not saying using cmder in vscode, I'm talking about using cmder.exe for debug |
I am not a VS Code user but many of our users are and this is how they integrate cmder, I assume for the same purpose you are trying to do. @DRSDavidSoft can you look at this and confirm? It does not look the same but maybe you can make some recommendations. |
@smgg I am not sure if the below would work but it looks to me like this might achieve what you want ASSUMING it is valid: Note: Substitute [cmder_root] with your Cmder installation directory.
|
@smgg & @daxgames – Sorry for the late response. I'd like to clear some up some information on the way both Cmder and VS Code. Hopefully this can also be used a future reference for similar problems. TL;DR: make sure you are on the latest version and also whether you get the same error message if you get the same error message when you launch the terminal directly (and not using the debug menu) I decided to write a complete explanation on how Cmder and VS Code work internally for future references. Cmder is a software packageA rather important thing to grasp on is that Cmder is not a stand-alone executable, but a collection of different software items that are packaged together in order to provide a complete terminal. For the sake of simplicity, I break up the contents to the following:
Whenever Cmder.exe is launched, a new console window is created and loaded with the Cmder shell. This is the typical window you see when you double-click on the Cmder.exe binary: Cmder is packaged with ConEmu as the console window, and uses clink with some special configuration as the default shell. The window you see in the above photo, is actually the packaged ConEmu that emulates the terminal in a window. As @daxgames said, the Cmder.exe binary is just a launcher that opens the ConEmu with the Cmder shell. (The main core of Cmder is a batch file located at How the terminal in VS Code worksThere are actually two different modes that the VS Code terminal operates in:
How do they differ?
Here's a demo of the first mode: Here's the relevant configuration for both methods: "terminal.integrated.shell.windows": "cmd.exe",
"terminal.integrated.shellArgs.windows": [
"/k", "%CMDER_ROOT%\\vendor\\init.bat"
],
"terminal.external.windowsExec": "C:\\path\\to\\cmder\\Cmder.exe", Now I'm not quite sure as to why @smgg would like to use the external window method instead of the integrated method, but the above configuration should work just fine in this case. There are a couple things I need to mention:
|
@DRSDavidSoft Thanks for the write-up. I am not a VSCode user so I was guessing. That is why I asked you to chime in since I know you could help. |
When I use vs Code debug and set the terminal to cmder, I got this Error
this is the configuration in vs Code
Can anybody help me out
The text was updated successfully, but these errors were encountered: