nvf/docs/manual/configuring/overriding-plugins.md
NotAShelf 8050617656
docs/manual: add custom keybinds section; minor wording tweaks
Co-Authored-by: horriblename <badnam3o.0@gmail.com>

Signed-off-by: NotAShelf <raf@notashelf.dev>
Change-Id: Idefa75ca9a92f89d008977a88066515d6a6a6964
2026-01-27 12:01:15 +03:00

1.1 KiB

Overriding plugins

The additional plugins section details the addition of new plugins to nvf under regular circumstances, i.e. while making a pull request to the project. You may override those plugins in your config to change source versions, e.g., to use newer versions of plugins that are not yet updated in nvf.

vim.pluginOverrides = {
  lazydev-nvim = pkgs.fetchFromGitHub {
    owner = "folke";
    repo = "lazydev.nvim";
    rev = "";
    hash = "";
  };
 
 # It's also possible to use a flake input
 lazydev-nvim = inputs.lazydev-nvim;
 # Or a local path 
 lazydev-nvim = ./lazydev;
 # Or a npins pin nvfetcher source, etc.
};

This will override the source for the lazydev.nvim plugin that is used in nvf with your own plugin.

::: {.warning}

While updating plugin inputs, make sure that any configuration that has been deprecated in newer versions is changed in the plugin's setupOpts. If you depend on a new version, requesting a version bump in the issues section is a more reliable option.

:::