4 ms·
If I'm on somebody else's system and need to hit the ground running Right Now then this comes into play instead - https://trout.me.uk/X11/vimrc https://trout.me
by mst 2y ago
If I'm on somebody else's system and need to hit the ground running Right Now then this comes into play instead - https://trout.me.uk/X11/vimrc https://trout.me.uk/X11/vimrc (I think it's been a few years now since I've been annoyed enough by something in vim to figure out how to turn it off and add yet another line to that ;)
- nocman 2y agoOut of curiosity, why bother to unmap the cursor keys? I don't ever use them in vim either, but is there something that is prevented from working with having them mapped in vim?
- baobun 2y agoIt can be useful to crush old habits. Also very useful if you do a lot of context switching or are an occasional user, to make sure your brain and fingers are in "vim mode" (at least one other line in the file makes this rather obvious) And once it's there, why bother removing it? I think you are in minority if you actively prune your vimrc for dead config...
- mst 2y agoI never had those habits, though I have passed that stanza on to people who were just learning to help remind them to use hjkl. I just tend to turn off things I only ever hit by accent (see also the :h override).
- mst 2y agoBecause I don't ever hit them except by accident while using vi(m) so disabling means an accidental keypress does nothing rather than something I didn't want. (my main reason for preferring original ex-vi is that when I typo a command, it beeps at me, whereas in vim the typo is usually some completely unrelated but valid command sequence and then WTF JUST HAPPENED and argh)