@@ -48,7 +48,7 @@ neovim.override {
4848
4949## Managing plugins with Vim packages
5050
51−To store you plugins in Vim packages the following example can be used:
51+To store you plugins in Vim packages (the native vim plugin manager, see `:help packages`) the following example can be used:
5252
5353```
5454vim_configurable.customize {
@@ -56,6 +56,8 @@ vim_configurable.customize {
5656 # loaded on launch
5757 start = [ youcompleteme fugitive ];
5858 # manually loadable by calling `:packadd $plugin-name`
59+ # however, if a vim plugin has a dependency that is not explicitly listed in
60+ # opt that dependency will always be added to start to avoid confusion.
5961 opt = [ phpCompletion elm-vim ];
6062 # To automatically load a plugin when opening a filetype, add vimrc lines like:
6163 # autocmd FileType php :packadd phpCompletion
@@ -63,6 +65,7 @@ vim_configurable.customize {
6365}
6466```
6567
68+`myVimPackage` is an arbitrary name for the generated package. You can choose any name you like.
6669For Neovim the syntax is:
6770
6871```
@@ -74,6 +77,8 @@ neovim.override {
7477 packages.myVimPackage = with pkgs.vimPlugins; {
7578 # see examples below how to use custom packages
7679 start = [ ];
80+ # If a vim plugin has a dependency that is not explicitly listed in
81+ # opt that dependency will always be added to start to avoid confusion.
7782 opt = [ ];
7883 };
7984 };