Published: November 26, 2020 • 4 min read
I am obsessed with Vim. Folks who’ve programmed with me, or attended the Vim Chicago Meetup when I was an active organizer, can attest. Vim is part of my developer origin story and it’s part of my identity as a developer. Any skill I have as a programmer started with gaining competence in Vim.
Should you learn Vim? I think so. I hope to make that case in an upcoming post.
A Vim developer is only as good as their Vim configuration file,
.vimrc1. In that spirit, here is my personal
.vimrc is broken up into three groups: settings, mappings, and
filetype-specific settings. If you open this file in Vim, you’ll see why: it’s
long, and it’s folded up by groups as a default. This is one of many tips I
picked up reading Learn VimScript The Hard
Way by Steve Losh, and the
dotfiles of programmers I admire.
What have I missed? What could I be doing better? I welcome pull request on my dotfiles repo. Even if I don’t merge the changes, we’ll both learn something.
Interested in copying this file on your root directory, along with the rest of my dotfiles? That’s not a bad a idea. Alternatively, you could build your own from scratch. You’ll learn more about what you value as a developer in that simple exercise than you’ll learn from a thousand Vim blog posts like this one. Good luck!
I posted this on Reddit and got a lot of attention! Some smart folks
helped me improve my workflow; the
.vimrc shown here reflects some of their
suggestions. I want to give credit to folks who took the time to contribute,
and also direct future feedback (which I still welcome) to settings that I’m
✉️ Get better at programming by learning with me. Subscribe to Jake Worth's Newsletter for bi-weekly ideas, creations, and curated resources from across the world of programming. Join me today!
Blog of Jake Worth, software engineer in Maine.