Add this line to the end of the JSON: "Ctrl-w": "CommandMode".Open %userprofile%/.config/micro/bindings.json with any editor.Here are the steps from the documentation to change it to ctrl + w (or whatever else non-conflicting keybinding of your own liking) on a Windows machine: Personally, I preferred to change Micro's ctrl + e. So you have to change the ctrl + e keybinding either on VSCode or on Micro to get rid of this conflict and then you're all set. To enable " command mode" on Micro, you have to use ctrl + e, which is also a keybinding of VSCode for the "Go To File." command. So you can type commands and you're fine to use Micro on VSCode as well. For instance, to quit Micro, you will have to use ctrl + q while it is the VSCode's keybinding for the "Quick Open View" command.īut no worries! Micro also supports "Typed Commands" which allow you to control the editor using commands instead of keybindings. Since both VSCode and Micro try to support all common keybindings, you'll probably have a lot of conflicting keybindings between them when using Micro inside the VSCode's embedded CMD/PowerShell terminal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |