(move content back in from plugin page) |
(remove redundant plugin link) |
||
Line 4: | Line 4: | ||
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. |
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. |
||
− | |||
− | {{script|id=2332|text=Download}} |
||
==Comments== |
==Comments== |
Revision as of 15:24, 5 October 2012
Use this page to discuss script 2332 Pathogen: easy manipulation of runtimepath, path, tags, etc.
- Add constructive comments, bug reports, or discuss improvements (see the guideline).
- Do not document the script here (the author should do that on vim.org).
- This page may be out of date: check the script's vim.org page above, and its release notes.
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.
Comments
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)