Overview

Using this repo as your .vim

First off, you're nuts. I suggest you create your own, using my .gitmodules as a guideline for creating your own. At a minimum, you should fork this so you can make your own changes.

Secondly, there's a Fabfile to take care of most of the work for you. Simply:

git clone https://bitbucket.org/jamezpolley/dot-vim.git .vim
cd .vim
fab update

Thirdly, you'll need to add a few lines to your .vimrc in order to infect Vim with pathogen, which will then take care of activating the rest of the bundles:

"Enable Pathogen
runtime bundle/vim-pathogen/autoload/pathogen.vim
call pathogen#infect()
call pathogen#helptags()

Top features

vimrc

gui options

I switch between using MacVim/Gvim and console vim. I like to have a light background when I'm running a GUI client, but dark on the console. The if has("gui_running") stanza near the top of the file accomplishes this, and also sets an appropriate font depending on the platform.

python-inspired

I work in Python a lot, so I always like to be aware of trailing whitespace and hard tab characters. I also like to be reminded when a line goes over 80 characters wide. The list/listchars options help with the first two, while the HighlightTooLongLines() function looks after the latter.

The Pylint() function calls pylint on the current file, and I have this mapped to \l for easy access. Since I started using the `Syntastic`_ plugin, I don't use this an awful lot.

Other filetype helpers

I edit restructered text a lot, so the rst reading helper maps h to a sequence of keystrokes that makes it it easy for me to create headings.

I have ,x, ,h, and ,j mapped to external commands which tidy up xml, html, and json respectively. I don't edit these a lot, but when I do, I like to stay sane.

I rely on Ctags a lot, so I have \C mapped to an external call to generate generates tags for me. I don't use this a lot any more, thanks to `tagbar`_ and `easytags`_