|
|
|
|
|
|
by maskedSlacker
3191 days ago
|
|
|
And the key bindings are lousy. But, setting that aside, I was begrudgingly impressed. I was conditioned at an impressionable age to be revolted by anything Microsoft, and VS Code mostly won me over. I still prefer emacs, but only because I haven't managed to customize VS Code to match my workflow (that might be impossible for now given that I spend about half my time working in Clojure). |
|
|
The key bindings are incredibly configurable and recent versions have added a really nice GUI for it (over just manually editing the JSON configs).
https://code.visualstudio.com/docs/getstarted/keybindings
The configuration of key bindings has been put through the ringer by the vscodevim extension, which has long been one of the "first customers" of the key binding configurations. If Vim can bind a key to it, for the most part so can you. There are very few functions in the application that you can't key bind if you wish.
Furthermore, extensions can contribute key maps and there are key map extensions based on a number of other editors already as extensions. A link right below the key binding configuration takes you to a recommended extension list.
It is interesting that VSCode defaults to a relatively small key map, encouraging you to explore commands through the command palette instead, but VSCode seems to make up for that by giving you a lot of power to customize as you see fit (and extension capabilities to share those customizations with others).