The only snag I’ve encountered is that the extension has updated their commands a couple times since I first set this up, but when that happens I just check back to the keybindings.json file in their repo and updated my command names accordingly (last updated in this post on July 20, 2021).Visual Studio Code, or VS Code for short, is a free and open source code editor by Microsoft. Place your key bi n di n gs i n t his f ile t o override t he de faults Here are the overrides that I have applied in my environment: As seen below, any commands that include “meta” in this file should be “alt” in your keyboard shortcuts JSON file.Įnter your overrides! In my examples below, I’m removing key binding rules from the extension by putting a “-” in front of the command name. Take a look at the keybindings.json file from the emacs-mcx repo to see the rules it applies. In VS Code go to Code > Preferences > Keyboard Shortcuts I achieved these changes with the following steps: My main issue was with the find widget closing when I didn’t it want to. I landed on Awesome Emacs Keymap (emacs-mcx).Īfter installing it, almost everything seemed right, but-like any Emacs user who is used to customizing things-I was running into a couple design decisions by the extension that I wanted to change. I looked for something that would be simple and would give me all the core commands I wanted while not getting in the way of the other useful things VSCode has to offer.
Naturally, there are extensions to solve this problem. This is a great head start to using those key bindings in another IDE, but it’s not enough.
I really like how a lot of the Emacs key bindings just work on Mac OSX. However, once I started writing a lot of TypeScript all the checking, completion, refactoring, etc. I used to write code entirely in Emacs, except when working with Java and the need for a heavier IDE would present itself. I’ve been working in Visual Studio Code a lot these days.
0 kommentar(er)
