If an IDE doesn’t have vi key bindings it isn’t going to be used by me. That’s what finally get me to change from terminal only dev to vscode. Until I found the vi editing extension the IDE wasn’t of interest.
Yes, vi is just that good.
I hear emacs bindings are also great, but I just know how to save and exit from emacs.
I use doom emacs and have to say, it takes everything that I like about vim and adds to emacs, plus a lot of useful features that i would have to install myself otherwise that can be enable by just uncommenting a feel lines in the config file.
It’s can feel a bit bloated at first but allows me to have the perfect IDE (for me at least) in a matter of minutes.
And the best of all is that I don’t need to use the emacs keybinds if I don’t wanna (and I don’t).
If an IDE doesn’t have vi key bindings it isn’t going to be used by me. That’s what finally get me to change from terminal only dev to vscode. Until I found the vi editing extension the IDE wasn’t of interest.
Yes, vi is just that good.
I hear emacs bindings are also great, but I just know how to save and exit from emacs.
Emacs keybinds are fine, used them for some years. But once I tried modal bindings I never wanted to go back, “key-chords” just add strain.
Fortunately emacs has many options for modal keybindings, I prefer meow over vim personally
I use doom emacs and have to say, it takes everything that I like about vim and adds to emacs, plus a lot of useful features that i would have to install myself otherwise that can be enable by just uncommenting a feel lines in the config file.
It’s can feel a bit bloated at first but allows me to have the perfect IDE (for me at least) in a matter of minutes.
And the best of all is that I don’t need to use the emacs keybinds if I don’t wanna (and I don’t).