-
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
Trying to get cmder in vscode working perfectly #1656
Comments
You have a key-shortcut conflict I just changed the key-mapping for cmder. Instead of hiding/showing on ctrl+` I changed it to win+` Or, you can change it for VSCode. |
@joekaiser asking for posterity, how did you change the cmder keymapping? (Is this a windows-level thing, or is it something I can find in the cmder settings?) |
Open your cmder preferences and change the keybinding there. |
Thanks! I feel stupid now. I was clicking through all of the sub-menus under "Keys & Macro". |
I've been trying to get cmder in my vscode environment as the terminal, and everything is working, minus the issue that when i press ctrl + ` and cmder is open, it switches to the open cmder instance.
This is very contrary to the expected behavior of vscode, which is that the terminal will open with a new instance of the terminal.
Dear developers, how do I make my current setup, which launches \vendor\init.bat with cmd /K, launch a new session of cmder in vscode? This would be a nice thing to get polished so that people can enjoy their cmder + vscode
The text was updated successfully, but these errors were encountered: