4 ms·
So, the first motivation for using vim is that you think it's readily available everywhere. However, the first thing you explain to me is how to remap the Esc k
by raimue 13y ago
So, the first motivation for using vim is that you think it's readily available everywhere. However, the first thing you explain to me is how to remap the Esc key. That is definitely not something configured everywhere.
For beginners with vim, just leave the Esc key as it is. It is way simpler to grasp the modes if a single key is required to switch. Also, you can just hammer a single key multiple times to get back to normal mode at all times.
Mapping keys are an advanced topic. That is not the first thing you should start with when explaining vim. Unexperienced users will not understand the significance.
- Crito 13y ago> "So, the first motivation for using vim is that you think it's readily available everywhere. [...] That is definitely not something configured everywhere." The aversion to custom settings is a rather uniquely "vim thing" (emacs people don't seem to do it), but I've never understood why it is a thing. I am probably temporarily annoyed by my missing custom settings once every year or two at most. Most machines I work with get my vim config lazily loaded as I use them. Where that isn't feasible/possible/permitted, the lack of my custom color scheme flips a bit in my brain and I naturally use the compat feature set. Custom settings not being ubiquitous is an objection that makes sense in theory, but it just doesn't seem to be an issue in reality to me. Honestly I have more trouble with ~/bin
- pessimizer 13y ago>Custom settings not being ubiquitous is an objection that makes sense in theory It makes sense if your reasoning for using vim is that it is ubiquitous.
- Crito 13y agoRight, but even if that is your reasoning, the objection does not hold if you observe reality. In reality, even ubiquity is a reason you use vim, custom settings aren't damaging.