kevin/vim-plug
1
Fork 0
mirror of https://github.com/junegunn/vim-plug.git synced 2024-12-19 10:35:38 -07:00
Code Issues Packages Projects Releases Wiki Activity

Updated faq (markdown)

Junegunn Choi 2017-01-30 00:40:48 +09:00
parent 8a5b36cd67
commit 7339b75e7d
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
faq.md

@ -151,6 +151,18 @@ augroup END
Yes, it automatically generates help tags for all of your plugins whenever you run `PlugInstall` or `PlugUpdate`. But you can regenerate help tags only with `plug#helptags()` function.
### When should I use `on` or `for` option?
_"Premature optimization is the root of all evil."_
You most likely don't need them at all. A properly implemented Vim plugin should already load lazily without any help from the plugin manager (`:help autoload`). There are very few cases where those options actually make much sense. On-demand loading should only be used as the last resort. It is basically a hacky workaround and is not guaranteed to work in every case.
Before applying the options, break down the startup of time of Vim using `--startuptime` first to identify the plugins that takes more than a few milliseconds.
```vim
vim --startuptime /tmp/log
```
### Shouldn't vim-plug update itself on `PlugUpdate` like Vundle?
There is a separate `PlugUpgrade` command and there are valid reasons behind the decision.