We’re going to take a look how to create your own
.vim config in a matter of minutes. There are many ways to do this. First one is pathogen, which I’m going to describe in this article, and then there’s also janus and vundle.
I prefer pathogen because it’s dead simple, you just need two lines in your
.vimrc. But let’s first do some initial setup:
$ take .vim # if you're using bash, just do mkdir & cd $ touch vimrc $ ln -s ~/.vim/vimrc ~/.vimrc $ git init $ git commit -m "Initial commit"
Now you’re ready to add pathogen to the mix.
call pathogen#runtime_append_all_bundles() call pathogen#helptags()
and add pathogen itself to
$ mkdir -p ~/.vim/autoload $ curl -Sso ~/.vim/autoload/pathogen.vim \ https://raw.github.com/tpope/vim-pathogen/master/autoload/pathogen.vim
That’s it, you’re done! Let’s just commit the changes.
$ git add vimrc $ git commit -m "Add pathogen config to .vimrc"
Pathogen uses git submodules for plugins, so it’s as easy as
$ git submodule add https://github.com/tpope/vim-rails.git bundle/rails
You can chose whatever name you want, just make sure it ends up in the bundle directory. Also let’s make sure we commit the addition.
$ git commit -m "Add rails.vim"
and the next time you run
vim, you’ll have the plugin automatically loaded.
When you want to clone the repository on a different machine, you also need to initialize the submodules. Let’s see how that would work.
$ git clone https://github.com/you/dotvim.git ~/.vim $ ln -s ~/.vim/vimrc ~/.vimrc $ cd ~/.vim $ git submodule init $ git submodule update
But what if you decide you don’t need a plugin anymore? You’re going to need to edit
.git/config and remove the submodule from both of the files.
After that just do
rm -rf bundle/foo and commit the changes.
We're building a tool to help businesses reach out to their customers more easily. It's called SendingBee and it's going to be awesome.