These are the vim runtime files that I use on a daily basis. Feel free to clone, modify, change, add, murder or remove portions of it at will.
I used to be a heavy advocate and user of Pathogen by the most excellent Tim Pope, but I have recently switched to Vundle, because I got tired of futzing around with git submodules every time I wanted to update or remove a bundle, but I still wanted a way of controlling my entire Vim runtime from some centralized source. Vundle seems to hit all the right sweet spots.
NOTE: If you have existing files in $HOME/.vim or $HOME/.vimrc, make sure you take appropriate backups before performing any of the following steps.
- First install Vundle, as per their instructions:
$ git clone http://github.com/gmarik/vundle.git ~/.vim/bundle/vundle- Next, get my vim-dotfiles & symlink the
.vimrcto your$HOME/.vimrc:
$ git clone [email protected]:jperras/vim-dotfiles.git ~/.vim && ln -s ~/.vim/.vimrc ~/.vimrc- Finally, we need to launch Vim and then invoke the appropriate Vundle commands to install all of the bundles using the
:BundleInstallcommand. When this is completed you'll need to build the C extension for the Command-T plugin plugin, which is a simple matter of cd'ing in to the command-t bundle folder and invokingrake make. I'm not quite sure if this process could somehow be automated with Vundle; if not, then that would be a fun addition to make to the project.
And that's it! Be sure to source your newly installed configuration (:source $MYVIMRC from inside Vim, or just restart a new editor session), and you should be good to go.
The included .vimrc contains some very minimal configurations that should be sane defaults for most developers, including a colorscheme that is pulled from one of the installed
bundles. Feel free to modify at will, of course. See the comments in the .vimrc file for more details, and check out the individual bundles that are pulled in on github until
I decide to annotate & comment on what each of them do.
And here's a gratuitous screenshot:
