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

docs: fix formatting

Browse source
This commit is contained in:
Soliprem 2025-12-11 15:39:41 +01:00
commit a951495882
3 changed files with 12 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

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

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

5
docs/manual/release-notes/rl-0.1.md
View file

@ -44,5 +44,6 @@ vim.luaConfigRC = lib.nvim.dag.entryAnywhere "config here"
[MoritzBoehme](https://github.com/MoritzBoehme): [MoritzBoehme](https://github.com/MoritzBoehme):
- `catppuccin` theme is now available as a neovim theme {option}`vim.theme.style` - `catppuccin` theme is now available as a neovim theme
and Lualine theme {option}`vim.statusline.lualine.theme`. {option}`vim.theme.style` and Lualine theme
{option}`vim.statusline.lualine.theme`.

4
docs/manual/release-notes/rl-0.7.md
View file

@ -301,8 +301,8 @@ The changes are, in no particular order:
controlling the default behaviour of the `nvim-navic` component on Lualine, controlling the default behaviour of the `nvim-navic` component on Lualine,
which used to occupy `winbar.lualine_c` as long as breadcrumbs are enabled. which used to occupy `winbar.lualine_c` as long as breadcrumbs are enabled.
- `vim.ui.breadcrumbs.alwaysRender` has been renamed to - `vim.ui.breadcrumbs.alwaysRender` has been renamed to
{option}`vim.ui.breadcrumbs.lualine.winbar.alwaysRender` to be conform to the {option}`vim.ui.breadcrumbs.lualine.winbar.alwaysRender` to be conform to
new format. the new format.
- Add [basedpyright](https://github.com/detachhead/basedpyright) as a Python LSP - Add [basedpyright](https://github.com/detachhead/basedpyright) as a Python LSP
server and make it default. server and make it default.