2024-04-20 03:57:11 +00:00
|
|
|
# Custom Plugins {#ch-custom-plugins}
|
|
|
|
|
2024-04-27 12:44:37 +00:00
|
|
|
**nvf**, by default, exposes a wide variety of plugins as module options
|
2024-09-13 17:01:33 +00:00
|
|
|
for your convenience and bundles necessary dependencies into **nvf**'s runtime.
|
2024-04-27 12:44:37 +00:00
|
|
|
In case a plugin is not available in **nvf**, you may consider making a pull
|
|
|
|
request to **nvf** to include it as a module or you may add it to your
|
|
|
|
configuration locally.
|
2024-04-20 03:57:11 +00:00
|
|
|
|
|
|
|
## Adding Plugins {#ch-adding-plugins}
|
|
|
|
|
2024-04-27 12:44:37 +00:00
|
|
|
There are multiple ways of adding custom plugins to your **nvf** configuration.
|
2024-04-20 03:57:11 +00:00
|
|
|
|
|
|
|
You can use custom plugins, before they are implemented in the flake. To add a
|
2024-04-27 12:44:37 +00:00
|
|
|
plugin to the runtime, you need to add it to the `vim.startPlugins` list in
|
|
|
|
your configuration.
|
2024-04-20 03:57:11 +00:00
|
|
|
|
|
|
|
Adding a plugin to `startPlugins` will not allow you to configure the plugin
|
2024-04-27 12:44:37 +00:00
|
|
|
that you have adeed, but **nvf** provides multiple way of configuring any
|
2024-04-20 03:57:11 +00:00
|
|
|
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
|
|
|
|
```
|