mirror of
https://github.com/NotAShelf/nvf.git
synced 2024-11-23 05:40:44 +00:00
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
# Legacy Method {#sec-legacy-method}
|
|
|
|
Prior to version v0.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
|
|
`vim.configRC` or `vim.luaConfigRC`. Users who have not yet updated to 0.5, or
|
|
prefer a more hands-on approach may use the old method where the load order of
|
|
the plugins is determined by DAGs.
|
|
|
|
## Adding plugins {#sec-adding-plugins}
|
|
|
|
To add a plugin not available in nvf as a module to your configuration, you may
|
|
add it to [](#opt-vim.startPlugins) in order to make it available to Neovim at
|
|
runtime.
|
|
|
|
```nix
|
|
{pkgs, ...}: {
|
|
# Add a Neovim plugin from Nixpkgs to the runtime.
|
|
vim.startPlugins = [pkgs.vimPlugins.aerial-nvim];
|
|
}
|
|
```
|
|
|
|
And to configure the added plugin, you can use the `luaConfigRC` option to
|
|
provide configuration as a DAG using the **nvf** extended library.
|
|
|
|
```nix
|
|
{inputs, ...}: let
|
|
# This assumes you have an input called 'nvf' in your flake inputs
|
|
# and 'inputs' in your specialArgs. In the case you have passed 'nvf'
|
|
# to specialArgs, the 'inputs' prefix may be omitted.
|
|
inherit (inputs.nvf.lib.nvim.dag) entryAnywhere;
|
|
in {
|
|
vim.luaConfigRC.aerial-nvim= entryAnywhere ''
|
|
require('aerial').setup {
|
|
-- your configuration here
|
|
}
|
|
'';
|
|
}
|
|
```
|