vim-plug/README.md

122 lines
4.4 KiB
Markdown
Raw Normal View History

2013-09-10 07:58:41 -07:00
vim-plug
========
2013-09-10 20:06:57 -07:00
A single-file Vim plugin manager.
2013-09-10 07:58:41 -07:00
2013-09-22 08:43:38 -07:00
Somewhere between [Pathogen](https://github.com/tpope/vim-pathogen) and
[Vundle](https://github.com/gmarik/vundle), but with faster parallel installer.
2013-09-18 05:26:15 -07:00
2013-09-23 21:10:57 -07:00
![](https://raw.github.com/junegunn/vim-plug/master/gif/vim-plug.gif)
2013-09-10 08:08:51 -07:00
### Pros.
2013-09-10 07:58:41 -07:00
2013-09-10 20:06:57 -07:00
- Easier to setup
2013-09-21 22:32:06 -07:00
- Parallel installation/update (requires
[+ruby](http://junegunn.kr/2013/09/installing-vim-with-ruby-support/))
2013-09-22 08:43:38 -07:00
- Smallest possible feature set
- Dependency resolution using `Plugfile` (experimental)
2013-09-10 07:58:41 -07:00
2013-09-10 08:08:51 -07:00
### Cons.
2013-09-10 07:58:41 -07:00
- Everything else
2013-09-10 07:58:41 -07:00
2013-09-10 08:08:51 -07:00
### Usage
2013-09-10 07:58:41 -07:00
2013-09-26 07:15:04 -07:00
[Download plug.vim](https://raw.github.com/junegunn/vim-plug/master/plug.vim)
and put it in ~/.vim/autoload
2013-09-10 07:58:41 -07:00
```sh
mkdir -p ~/.vim/autoload
2013-09-10 20:06:57 -07:00
curl -fLo ~/.vim/autoload/plug.vim https://raw.github.com/junegunn/vim-plug/master/plug.vim
2013-09-10 07:58:41 -07:00
```
Edit your .vimrc
```vim
2013-09-16 01:37:09 -07:00
call plug#begin()
2013-09-10 07:58:41 -07:00
Plug 'junegunn/seoul256'
Plug 'junegunn/vim-easy-align'
" Plug 'user/repo1', 'branch_or_tag'
" Plug 'user/repo2', { 'rtp': 'vim/plugin/dir', 'branch': 'devel' }
2013-09-16 20:35:10 -07:00
" Plug 'git@github.com:junegunn/vim-github-dashboard.git'
2013-09-10 07:58:41 -07:00
" ...
2013-09-16 01:37:09 -07:00
call plug#end()
2013-09-10 07:58:41 -07:00
```
2013-09-22 09:49:34 -07:00
Then `:PlugInstall` to install plugins.
### Plugin directory
By default, plugins are installed in `plugged` directory under the first path in
runtimepath at the point when `plug#begin()` is called. This is usually
2013-09-22 09:51:55 -07:00
`~/.vim/plugged` (or `$HOME/vimfiles/plugged` on Windows) given that you didn't
touch runtimepath before the call. You can explicitly set the location of the
plugins with `plug#begin(path)` call.
2013-09-10 07:58:41 -07:00
2013-09-10 08:08:51 -07:00
### Commands
2013-09-10 07:58:41 -07:00
2013-09-24 20:51:07 -07:00
| Command | Description |
| ---------------------- | ------------------------------------------------------------------ |
| PlugInstall [#threads] | Install plugins |
| PlugUpdate [#threads] | Install or update plugins |
| PlugClean[!] | Remove unused directories (bang version will clean without prompt) |
| PlugUpgrade | Upgrade vim-plug itself |
| PlugStatus | Check the status of plugins |
2013-09-10 08:08:51 -07:00
### Options for parallel installer
| Flag | Default | Description |
| ---------------- | ------- | --------------------------------- |
| `g:plug_threads` | 16 | Default number of threads to use |
| `g:plug_timeout` | 60 | Time limit of each task in seconds |
2013-09-10 07:58:41 -07:00
### Dependency resolution
If a Vim plugin specifies its dependent plugins in `Plugfile` in its root
directory, vim-plug will automatically source it recursively during the
installation.
A `Plugfile` should contain a set of `Plug` commands for the dependent plugins.
I've created three dummy repositories with Plugfiles as an example to this
scheme.
- [junegunn/dummy1](https://github.com/junegunn/dummy1/blob/master/Plugfile)
- Plugfile includes `Plug 'junegunn/dummy2'`
- [junegunn/dummy2](https://github.com/junegunn/dummy2/blob/master/Plugfile)
- Plugfile includes `Plug 'junegunn/dummy3'`
- [junegunn/dummy3](https://github.com/junegunn/dummy3/blob/master/Plugfile)
If you put `Plug 'junegunn/dummy1'` in your configuration file, and run
`:PlugInstall`,
1. vim-plug first installs dummy1
2. And sees if the repository has Plugfile
3. Plugfile is loaded and vim-plug discovers dependent plugins
4. Dependent plugins are then installed as well, and their Plugfiles are
examined and their dependencies are resolved recursively.
2013-09-26 03:09:54 -07:00
![](https://raw.github.com/junegunn/vim-plug/master/gif/Plugfile.gif)
2013-09-18 05:26:15 -07:00
### Articles
- [Writing my own Vim plugin manager](http://junegunn.kr/2013/09/writing-my-own-vim-plugin-manager)
2013-09-28 06:42:33 -07:00
- [Thoughts on Vim plugin dependency](http://junegunn.kr/2013/09/thoughts-on-vim-plugin-dependency)
2013-09-18 05:26:15 -07:00
2013-09-24 07:15:31 -07:00
### Regarding feature request
You may submit a request for a new feature by [creating an
issue](https://github.com/junegunn/vim-plug/issues). However, please be minded
that this is an opinionated software and I want to keep the feature set as small
as possible. So I may not agree with you on the necessity of the suggested
feature. If that happens, I suggest the following options.
1. Check out [Vundle](https://github.com/gmarik/vundle) or
[NeoBundle](https://github.com/Shougo/neobundle.vim).
They offer broader feature sets.
2. Create a fork of this project and let it be your own plugin manager.
There's no need for us to have a single canonical branch.