mirror of
https://github.com/NotAShelf/nvf.git
synced 2024-11-30 00:26:45 +00:00
doc: update configuration docs on custom plugins
This commit is contained in:
parent
02676d4224
commit
850465faba
5 changed files with 73 additions and 12 deletions
|
@ -20,6 +20,7 @@ custom plugins that you might have added to your configuration.
|
|||
|
||||
```{=include=} sections
|
||||
custom-plugins/configuring.md
|
||||
custom-plugins/new-method.md
|
||||
custom-plugins/old-method.md
|
||||
custom-plugins/lazy-method.md
|
||||
custom-plugins/non-lazy-method.md
|
||||
custom-plugins/legacy-method.md
|
||||
```
|
||||
|
|
|
@ -1,12 +1,32 @@
|
|||
# Configuring {#sec-configuring-plugins}
|
||||
|
||||
Just making the plugin to your Neovim configuration available might not always
|
||||
be enough. In that case, you can write custom lua config using either
|
||||
`config.vim.extraPlugins` (which has the `setup` field) or
|
||||
`config.vim.luaConfigRC`. The first option uses an attribute set, which maps DAG
|
||||
section names to a custom type, which has the fields `package`, `after`,
|
||||
`setup`. They allow you to set the package of the plugin, the sections its setup
|
||||
code should be after (note that the `extraPlugins` option has its own DAG
|
||||
Just making the plugin to your Neovim configuration available might not always be enough. In that
|
||||
case, you can write custom lua config using either `config.vim.lazy.plugins.*.setupOpts`
|
||||
`config.vim.extraPlugins.*.setup` or `config.vim.luaConfigRC`.
|
||||
|
||||
The first option uses an extended version of `lz.n`'s PluginSpec. `setupModule` and `setupOpt` can
|
||||
be used if the plugin uses a `require('module').setup(...)` pattern. Otherwise, the `before` and
|
||||
`after` hooks should do what you need.
|
||||
|
||||
```nix
|
||||
{
|
||||
config.vim.lazy.plugins = {
|
||||
aerial-nvim = {
|
||||
# ^^^^^^^^^ this name should match the package.pname or package.name
|
||||
package = aerial-nvim;
|
||||
|
||||
setupModule = "aerial";
|
||||
setupOpts = {option_name = false;};
|
||||
|
||||
after = "print('aerial loaded')";
|
||||
};
|
||||
};
|
||||
}
|
||||
```
|
||||
|
||||
The second option uses an attribute set, which maps DAG section names to a custom type, which has
|
||||
the fields `package`, `after`, `setup`. They allow you to set the package of the plugin, the
|
||||
sections its setup code should be after (note that the `extraPlugins` option has its own DAG
|
||||
scope), and the its setup code respectively. For example:
|
||||
|
||||
```nix
|
||||
|
@ -24,7 +44,7 @@ config.vim.extraPlugins = with pkgs.vimPlugins; {
|
|||
}
|
||||
```
|
||||
|
||||
The second option also uses an attribute set, but this one is resolved as a DAG
|
||||
The third option also uses an attribute set, but this one is resolved as a DAG
|
||||
directly. The attribute names denote the section names, and the values lua code.
|
||||
For example:
|
||||
|
||||
|
|
40
docs/manual/configuring/custom-plugins/lazy-method.md
Normal file
40
docs/manual/configuring/custom-plugins/lazy-method.md
Normal file
|
@ -0,0 +1,40 @@
|
|||
# Lazy Method {#sec-lazy-method}
|
||||
|
||||
As of version **0.7**, we exposed an API for configuring lazy-loaded plugins via
|
||||
`lz.n` and `lzn-auto-require`.
|
||||
|
||||
```nix
|
||||
{
|
||||
config.vim.lazy.plugins = {
|
||||
aerial = {
|
||||
package = pkgs.vimPlugins.aerial-nvim;
|
||||
setupModule = aerial;
|
||||
setupOpts = {
|
||||
option_name = true;
|
||||
};
|
||||
after = ''
|
||||
-- custom lua code to run after plugin is loaded
|
||||
print('aerial loaded')
|
||||
'';
|
||||
|
||||
# Explicitly mark plugin as lazy. You don't need this if you define one of
|
||||
# the trigger "events" below
|
||||
lazy = true;
|
||||
|
||||
# load on command
|
||||
cmd = ["AerialOpen"];
|
||||
|
||||
# load on event
|
||||
event = ["BufEnter"];
|
||||
|
||||
# load on keymap
|
||||
keys = [
|
||||
{
|
||||
key = "<leader>a";
|
||||
action = ":AerialToggle<CR>";
|
||||
}
|
||||
];
|
||||
};
|
||||
};
|
||||
}
|
||||
```
|
|
@ -1,4 +1,4 @@
|
|||
# Old Method {#sec-old-method}
|
||||
# Legacy Method {#sec-legacy-method}
|
||||
|
||||
Prior to version 0.5, the method of adding new plugins was adding the plugin
|
||||
package to `vim.startPlugins` and add its configuration as a DAG under one of
|
|
@ -1,4 +1,4 @@
|
|||
# New Method {#sec-new-method}
|
||||
# Non-lazy Method {#sec-non-lazy-method}
|
||||
|
||||
As of version **0.5**, we have a more extensive API for configuring plugins,
|
||||
under `vim.extraPlugins`. Instead of using DAGs exposed by the library, you may
|
Loading…
Reference in a new issue