Pathogen is a plugin-manager.
Manage your 'runtimepath' with ease. In practical terms, pathogen.vim makes it super easy to install plugins and runtime files in their own private directories.
This plugin seems really very good. But does it work with vimballs? In other words how does pathogen manage plugins installed by vimball, if at all? --May 27, 2011
- There are instructions about UseVimball on http://github.com/tpope/vim-pathogen. --July 19, 2012
The directions to use curl given on this page did not work for me (I just get a bunch of html on the command line). The directions on github.com/tpope/ work fine. When I have time to figure out curl I'll determine what I did wrong. Until then:
mkdir -p ~/.vim/autoload ~/.vim/bundle curl -so ~/.vim/autoload/pathogen.vim \ https://raw.github.com/tpope/vim-pathogen/HEAD/autoload/pathogen.vim
--March 5, 2012
- I made a small tweak to your post (no need for "; \" on the first line). The instructions given on the script page do work. JohnBeckett 06:53, March 5, 2012 (UTC)
A comment was posted July 23, 2014 with a link using a redirector. I don't think that is a good idea because while it possibly works now, no one can know what a redirector is doing. This page is for users of the script to comment on it, and we should not second-guess the documentation. If the person who posted the comment (which I have removed) wants, perhaps explain why a redirector is needed. Presumably the URL in the 2012 comment above was taken from documentation at the time (although the removed comment states it is now wrong), and adding more URLs here is not going to help. Let's point to the documentation page. JohnBeckett (talk) 06:04, July 28, 2014 (UTC)
February 24, 2015
I could not make work pathogene in gVim. For all settings I used a _gvimrc - file, which worked fine except the pathogene plugin did not load the plugins. Then I renamed the _gvimrc to _vimrc and it worked. Is this a bug?!
- Not a bug, it's just a quirk of how Vim works. Plugins are loaded after the vimrc, but before the gvimrc. Thus setting up pathogen does not work in the gvimrc, because it is too late at that point. Note that you can have both a vimrc and a gvimrc; gvim will read both of them. See :help startup for details. --Fritzophrenic (talk) 16:11, February 24, 2015 (UTC)