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 = {
+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";
@@ -1208,8 +1208,8 @@ functions. There are many settings available in the options. Please refer to the
documentation to
-see a list of them.
nvf provides a helper function, so that you don’t have to write the
-mapping attribute sets every time:
mkKeymap, which mimics neovim’s vim.keymap.set function
You can read the source code of some modules to see them in action, but the
+see a list of them.
nvf provides a helper function, so that you don’t have to write the mapping
+attribute sets every time:
mkKeymap, which mimics neovim’s vim.keymap.set function
You can read the source code of some modules to see them in action, but the
usage should look something like this:
# plugindefinition.nix
{lib, ...}: let
inherit (lib.options) mkEnableOption;