2 ms·
Tip (not really ontopic): learn Vim, then use whatever editor or IDE you want with Vim keybindings mode or a Vim-emulating plugin - you'll end up with an univer
by nnq 14y ago
Tip (not really ontopic): learn Vim, then use whatever editor or IDE you want with Vim keybindings mode or a Vim-emulating plugin - you'll end up with an universal set of keybindings you will learn once and use everywhere and you will be able to be productive in any editor and any IDE (yeah, there are always limitations, nothing emulates Vim perfectly and this is way I advise you "not to learn too much of real vim", just the most usefull keys, but nowadays there is at leas one good vim mode/plugin for any other serious IDE or editor, including ST2).
- newishuser 14y agoWhile you are correct, you are completely off topic and not really helping. Plus, it's not like HN needs another reminder of vim's infallibility.
- nnq 14y agoit's not about vim's infallibility - I consider vim ugly, weird, too powerful and ad the same time limited and I'm a ST user. I was just referring to the fact that by learning its keys and basic modal principles, you can afford not to learn 70% of the fucked-up keystrokes and menu driven functionality of other otherwise good editors or IDEs. Just learn the 30% that is really unique and useful (GUI stuff, advanced refactoring etc.) and "drive it like it's vim" for other features. This way it becomes like driving cars: 90% of car functionality is the same for all cars so I can jump into any car and drive it - maybe not for best safety and performance, but it works for me.