NotAShelf/nvf
2
1
Fork 0
mirror of https://github.com/NotAShelf/nvf.git synced 2025-12-11 22:53:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

treewide: replace auto option links with {option} role

Browse source
This commit is contained in:
Ching Pei Yang 2025-12-11 15:15:58 +01:00
commit da8c682af7
No known key found for this signature in database
GPG key ID: B3841364253DC4C8
16 changed files with 58 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -19,7 +19,7 @@ as a module.
:::{.info}
To add a plugin to your runtime, you will need to add it to
[](#opt-vim.startPlugins) list in your configuration. This is akin to cloning a
{option}`vim.startPlugins` list in your configuration. This is akin to cloning a
plugin to `~/.config/nvim`, but they are only ever placed in the Nix store and
never exposed to the outside world for purity and full isolation.

6
docs/manual/configuring/custom-plugins/legacy-method.md
View file

@ -1,8 +1,8 @@
# Legacy Method {#sec-legacy-method}
Prior to version **0.5**, the method of adding new plugins was adding the plugin
package to [](#opt-vim.startPlugins) and adding its configuration as a DAG under
one of `vim.configRC` or [](#opt-vim.luaConfigRC). While `configRC` has been
package to {option}`vim.startPlugins` and adding its configuration as a DAG under
one of `vim.configRC` or {option}`vim.luaConfigRC`. While `configRC` has been
deprecated, users who have not yet updated to 0.5 or those who prefer a more
hands-on approach may choose to use the old method where the load order of the
plugins is explicitly determined by DAGs without internal abstractions.
@ -10,7 +10,7 @@ plugins is explicitly determined by DAGs without internal abstractions.
## Adding New Plugins {#sec-adding-new-plugins}
To add a plugin not available in **nvf** as a module to your configuration using
the legacy method, you must add it to [](#opt-vim.startPlugins) in order to make
the legacy method, you must add it to {option}`vim.startPlugins` in order to make
it available to Neovim at runtime.
```nix

2
docs/manual/configuring/custom-plugins/non-lazy-method.md
View file

@ -2,7 +2,7 @@
As of version **0.5**, we have a more extensive API for configuring plugins that
should be preferred over the legacy method. This API is available as
[](#opt-vim.extraPlugins). Instead of using DAGs exposed by the library
{option}`vim.extraPlugins`. Instead of using DAGs exposed by the library
_directly_, you may use the extra plugin module as follows:
```nix