Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
My vim config
VimL Python Makefile TeX C Shell Other
branch: master
Failed to load latest commit information.
autoload First commit, added EVRYTHIN git add .gitignore
bundle-available
bundle replace zencoding with emmet
colors add colorschemes slate{,2}
doc First commit, added EVRYTHIN git add .gitignore
ftplugin moved autcppcomplete to ftplugin
plugin remove twitter
syntax add syntax for conkyrc files
.gitignore add undo file to gitignore
.gitmodules replace zencoding with emmet
README.md Edited README.md via GitHub
c-support First commit, added EVRYTHIN git add .gitignore
tags added tags
vimrc set tab width to 2 all the time

README.md

My one and only vim config

This is the .vim & .vimrc files that I use everywhere I can use vim and git my config. I could improve a lot of things, starting with a special colorscheme on non 256-colors terminals. plus some scripts to automate the activation of modules and the installation of .vimrc on a new computer

requirements

  • vim 7.2 (ubuntu package)
  • ruby (for command-t)
  • 256-colors terminal

bundles

this config uses pathogen which is just awesome. It allows to separate bundles in their own directories instead of putting everything in the ~/.vim root.

add a bundle

In order to install a new bundle, one must add it in the bundle-available directory.

activate a bundle

those of you who are familiar with pathogen know that bundles live in the bundle directory. In order to be able to activate/deactivate bundles everything in bundle is a symlink to the real module in bundle-available

more

I'm looking for a way to handle per-project activation of bundles because I don't need omnicppcomplete everyday and I want to deactivate it most the time

forking

You can fork my config, I would be happy to get pull requests as well

Something went wrong with that request. Please try again.