diff options
author | ryneeverett <ryneeverett@gmail.com> | 2020-03-28 17:42:31 +0000 |
---|---|---|
committer | ryneeverett <ryneeverett@gmail.com> | 2020-04-01 14:30:39 +0000 |
commit | f1ae95f6d3cbc55cea72fe2765105a6b998ec7db (patch) | |
tree | 38c976ff3d17cdbe0e91beed0298ab7ccc030a14 /doc | |
parent | 042c3dc356f24af8b6b87db1dbda335b4b0c535c (diff) |
vimPlugins: update.py --add <plugin> argument
- update.py's new --add argument replaces manual editing of
vim-plugin-names for basic use cases.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/languages-frameworks/vim.section.md | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/doc/languages-frameworks/vim.section.md b/doc/languages-frameworks/vim.section.md index 4272d1f59691..1d316cf350e5 100644 --- a/doc/languages-frameworks/vim.section.md +++ b/doc/languages-frameworks/vim.section.md @@ -261,12 +261,7 @@ deoplete-fish = super.deoplete-fish.overrideAttrs(old: { Sometimes plugins require an override that must be changed when the plugin is updated. This can cause issues when Vim plugins are auto-updated but the associated override isn't updated. For these plugins, the override should be written so that it specifies all information required to install the plugin, and running `./update.py` doesn't change the derivation for the plugin. Manually updating the override is required to update these types of plugins. An example of such a plugin is `LanguageClient-neovim`. -To add a new plugin: - - 1. run `./update.py --commit`, - 2. add the new plugin to [vim-plugin-names](/pkgs/misc/vim-plugins/vim-plugin-names) and add overrides if required to [overrides.nix](/pkgs/misc/vim-plugins/overrides.nix), - 3. run `./update.py` again and create a commit named "vimPlugins.[name]: init at [version]" (where `name` and `version` can be found in [generated.nix](/pkgs/misc/vim-plugins/generated.nix)), and - 4. create a pull request. +To add a new plugin, run `./update.py --commit --add "[owner]/[name]"`. ## Important repositories |