Skip to content

Commit

Permalink
Set up Pathogen boilerplate
Browse files Browse the repository at this point in the history 
We're going to be using the Vim plugin manager called Vundle.

NOTE

For this talk, I'm assuming that you're starting from a blank slate. If
you have a ~/.vim folder, move it out of the way:

    mv ~/.vim ~/.vim.old

INSTALLATION INSTRUCIONS

Before making these changes, you'll need to install Vundle. Run this
command to install it:

    git clone https://github.com/gmarik/Vundle.vim
~/.vim/bundle/Vundle.vim

This installs Vundle.vim to a subdirectory of your ~/.vim folder. We'll
be using Vundle in upcoming steps to add lots of plugins!

The changes we made in this step are outlined right on the front page of
the Vundle project page on GitHub. They're just stock changes that need
to be made for Vundle to work.
  • Loading branch information
@jez
jez committed Feb 25, 2015
1 parent fc77b04 commit 1186be2
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions vimrc.vim
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,17 @@
" Gotta be first
set nocompatible

filetype off

set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()

Plugin 'gmarik/Vundle.vim'

call vundle#end()

filetype plugin indent on

" --- General settings ---
set backspace=indent,eol,start
set ruler
Expand Down

7 comments on commit 1186be2

@jez
Copy link
Owner Author

@jez jez commented on 1186be2 Feb 26, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(<-- prev step) ... (next step -->)

As was mentioned in the talk, Vundle is actually not actively maintained. The good thing is that it basically works fine right now, but you may want to consider alternative plugin managers.

The definitive plugin manager is Pathogen, which gives you ultimate control over plugins but is hard to use well. This is the manager that I use.

The plugin manager that was recommend by an audience member was vim-plug, which at first glance looks like it's pretty solid.

@daenney
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also NeoBundle. Builds on Vundle's legacy.

@n0nick
Copy link

@n0nick n0nick commented on 1186be2 Feb 26, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The commit title (and your comment) says "Pathogen", but the commit message (and code) says "Vundle".
Which is it? :)

@jez
Copy link
Owner Author

@jez jez commented on 1186be2 Feb 26, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's Vundle haha XD I realized after I'd committed and pushed the README with all the commit hashes that the title was incorrect. If I rebase now, I'd have to rewrite the README and I'd probably loose all the comments on the GitHub commits... It's a lesson in proof reading :P

@AmmarCodes
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vim-Plug is amazing, probably you should give it a try!

@steve-lorimer
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on my understanding of the vim-plug installation instructions from here

Install vim-plug

$ curl -fLo ~/.vim/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim

Enable in ~/.vimrc

call plug#begin('~/.vim/plugged')

" plugins will go here (see next step) 
" (be sure to replace 'Plugin' with 'Plug')

call plug#end()

@sbhal
Copy link

@sbhal sbhal commented on 1186be2 Jun 10, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vim-Plug is the way to go. Amazingly fast.

Please sign in to comment.