Browse files

Merge pull request #1 from SethMilliken/patch-2

Updated pathogen installation instructions
  • Loading branch information...
2 parents 4d374c5 + 3276338 commit e2d55651e26cca6924ad5d0fd6792ae3eaff9bf8 Tammer Saleh committed Aug 31, 2011
Showing with 7 additions and 10 deletions.
  1. +7 −10 views/posts/the-modern-vim-config-with-pathogen.html.textile
@@ -1,8 +1,8 @@
-date: 2010-04-04
-title: The Modern Vim Config with Pathogen
+date: 2010-04-04
+title: The Modern Vim Config with Pathogen
Unix gets a "whole lot right":, but the way it dumps everything into the same filesystem isn't one of them. Traditionally, every application you install will put files under @/etc@, @/usr/bin@, @/var@, @/lib@, and so on. This makes it impossible to confidently extract an installed application, and lead to the development of "various": "package": "management": "tools":
h4. Vim's legacy
@@ -38,11 +38,8 @@ pathogen.vim
Now call pathogen from your @.vimrc@ like such:
-" Needed on some linux distros.
-" see
-filetype off
+call pathogen#infect()
call pathogen#helptags()
-call pathogen#runtime_append_all_bundles()
...and that's it! This is the only plugin you'll install directly into your @~/.vim@ directory. After that, any plugin you install into the @~/.vim/bundle@ directory will be seen by vim. At this point, you can start copying in the contents of your @.vimrc@ and @.gvimrc@ files, taking the time to clean them up as you go.
@@ -106,4 +103,4 @@ vim_org_scripts.each do |name, script_id, script_type|
file << open("{script_id}").read

0 comments on commit e2d5565

Please sign in to comment.