Investing time learning a text editor is a serious commitment. Over time, you find yourself reaching for the editor’s built-in shortcut keys everywhere you type. In my case, I do almost all of my writing in MacVim. Unfortunately, MacVim comes with a fairly steep learning curve that many are unwilling to tackle. Part of the complexity of Vim, from which MacVim is derived, is the configuration. Over the years I’ve come up with a setup that works for me.
My configuration is kept in Dropbox in a folder named Vim. I create three symlinks in my home directory.
ln -s ~/Dropbox/Vim ~/.vim ln -s ~/Dropbox/Vim/gvimrc ~/.gvimrc ln -s ~/Dropbox/Vim/vimrc ~/.vimrc
MacVim is customized through plugins. The history and legacy code behind the plugins make them unwieldy to maintain, so the first plugin I install is one to manage other plugins. Pathogen by Tim Pope allows you to use Git to install other plugins, and keep them nicely organized in
~/.vim/bundle. The GitHub page for Pathogen includes simple installation instructions. From here, to install other plugins, clone that plugin’s Git repository into the
I have found that the list of plugins I use changes every so often according to what language I’m working in or what task I’m working on. Vim is much like Linux… infinitely tweakable, and, if you are not careful, it can turn into a vast time sink. However, if you can curb your nerd impulse to optimize endlessly, and find a configuration that works for you, Vim will be your constant companion, always there for you when needed.
Subscribe via RSS