4 ms·
> To those who would say "that's obvious; of course you learn vim incrementally", I would simply say that having spoken to a number of vim users in the past, I
by raverbashing 7y ago
> To those who would say "that's obvious; of course you learn vim incrementally", I would simply say that having spoken to a number of vim users in the past, I never got that advice. Instead, I got a lot of advice about turning off my arrow keys, disallowing the use of the mouse, and learning the (MORE EFFICIENT!!!) vim ways to do everything, all at once
Ugh, this.
Arrow keys have been invented for a reason, they're good and intuitive and there's absolutely nothing wrong with using them. Same with the mouse.
The "pure" VIM ways are more efficient than ed. They're maybe more efficient some 10% of times you actually need some specific thing. But they're not better than a visual editor.
- Lio 7y ago"Pure" vim supports cursor keys, mouse, windows, syntax highlighting, fuzzy searching for files, filetree and a whole host of other features without the need for plugins. In what way is Vim not a "visual editor"? The main problem with using Vim is that you will spend a bit of time explaining to those that don't know it very well that it's actually perfectly capable of doing the thing they are using as justification that you should switch to their current favourite IDE/editor... :P
- awwaiid 7y agoI config vim to have a slightly different semantic for arrow keys vs hjkl. I leave hjkl as-is, and then make arrow keys move across visible screen lines. So if there is a long line that wraps, the down arrow moves down one visible line (so technically still within the long line), and j moves to the next actual line in the file. Handy. map <up> gk imap <up> <c-o>gk map <down> gj imap <down> <c-o>gj