Unix gets a "whole lot right":http://en.wikipedia.org/wiki/Unix_philosophy#Eric_Raymond, 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":http://en.wikipedia.org/wiki/RPM_Package_Manager "package":http://en.wikipedia.org/wiki/Debian#APT.2C_installing_packages_from_online_repositories "management":http://mxcl.github.com/homebrew/ "tools":http://en.wikipedia.org/wiki/Encap_Package_Management_System.
h4. Vim's legacy
@@ -38,11 +38,8 @@ pathogen.vim
Now call pathogen from your @.vimrc@ like such:
-" Needed on some linux distros.
-" see http://www.adamlowe.me/2009/12/vim-destroys-all-other-rails-editors.html
...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|