NotAShelf/nvf
2
1
Fork 0
mirror of https://github.com/NotAShelf/nvf.git synced 2025-09-06 10:21:31 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

docs: format via deno fmt

Browse source 
This should be a pre-commit hook in the future.
This commit is contained in:
raf 2024-11-25 19:16:46 +03:00
commit a196e9610f
Signed by: NotAShelf
GPG key ID: AF26552424E53993
11 changed files with 114 additions and 117 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/manual/configuring/custom-plugins.md
View file

@ -1,8 +1,8 @@
# Custom Plugins {#ch-custom-plugins}
**nvf**, by default, exposes a wide variety of plugins as module options
for your convenience and bundles necessary dependencies into **nvf**'s runtime.
In case a plugin is not available in **nvf**, you may consider making a pull
**nvf**, by default, exposes a wide variety of plugins as module options for
your convenience and bundles necessary dependencies into **nvf**'s runtime. 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.
@ -11,12 +11,12 @@ configuration locally.
There are multiple ways of adding custom plugins to your **nvf** configuration.
You can use custom plugins, before they are implemented in the flake. To add a
plugin to the runtime, you need to add it to the `vim.startPlugins` list in
your configuration.
plugin to the runtime, you need to add it to the `vim.startPlugins` list in your
configuration.
Adding a plugin to `startPlugins` will not allow you to configure the plugin
that you have adeed, but **nvf** provides multiple way of configuring any
custom plugins that you might have added to your configuration.
that you have adeed, but **nvf** provides multiple way of configuring any custom
plugins that you might have added to your configuration.
```{=include=} sections
custom-plugins/configuring.md