Something about fine tuning dotfiles triggers a chemical process in the
brain that demands personal
.vimrc evangelism, and despite my impending
participation I believe this zeal is a primary barrier to
the sort of standardization I think the Vim community needs.
That being the case, I wanted to preface my vim tip series with a few caveats
First, I’ll try to steer clear of “best practice” vim customizations that I think
people should (and probably do) already have somewhere in their dotfiles. These
have been written about ad nauseam elsewhere, so if you are still using
C-w, l to navigate split windows these probably aren’t for you. I’m certainly
not claiming novelty, just shooting for things that feel under-appreciated or
experimental. In general
I’ll avoid shortcuts and settings in the thoughtbot dotfiles since
those have been battle-tested by their team and well covered. Examples
include remapping your leader, setting line numbers and using
My local overrides focus mainly on two things:
- Reducing repetition. A never-ending game of Vim golf, what’s not to love?
- Reducing mistakes. Unfortunately I am not a great touch typist. Like many of my AIM-trained peers I am fast but error-prone, and Vim punishes you mercilessly for simple typing mistakes.
My solution to reducing typing errors while maintaining speed is first to improve my typing skill (this takes time), and second to map common vim commands in such a way that I don’t need to venture into challenging key zones (cough number keys cough) as often as I otherwise would. This means that many of my tips might seem amateurish or superfluous to more experienced developers with better typing skills, but I think the newest crop of Vim users will appreciate my little conveniences.
Hope you enjoy!