+
If your problem is caused by a bug in neovim-flake then it should be reported on the
neovim-flake issue tracker.
Alongside bug reports, feature requests are also welcome over
@@ -70,7 +70,10 @@ To add a plugin, you need to add it to your config’s However, just making the plugin available might not be enough. In that case, you can write custom vimscript or lua config, using Note: If your configuration needs to be put in a specific place in the config, you can use functions from Also, if you successfully made your plugin work, please make a PR to add it to the flake, or open an issue with your findings so that we can make it available for everyone easily.con
}config.vim.configRC or config.vim.luaConfigRC respectively.
These options are attribute sets, and you need to give the configuration you’re adding some name, like this:{
config.vim.configRC.aquarium = "colorscheme aquiarum";
-}inputs.neovim-flake.lib.nvim.dag to order it. Refer to https://github.com/nix-community/home-manager/blob/master/modules/lib/dag.nix.
The Home Manager module allows us to customize the different vim options. To use it, we first add the input flake.
{
+}Note: If your configuration needs to be put in a specific place in the config, you can use functions from inputs.neovim-flake.lib.nvim.dag to order it. Refer to https://github.com/nix-community/home-manager/blob/master/modules/lib/dag.nix.
Also, if you successfully made your plugin work, please make a PR to add it to the flake, or open an issue with your findings so that we can make it available for everyone easily.
As of v0.5, you may now specify the neovim package that will be wrapped with your configuration. This is done with the vim.package option.
{inputs, pkgs, ...}: {
+ # using the neovim-nightly overlay
+ config.vim.package = inputs.neovim-overlay.packages.${pkgs.system}.neovim;
+}The neovim-nightly-overlay always exposes an unwrapped package. If using a different source, you are highly recommended to get an "unwrapped" version of the neovim package,similar to neovim-unwrapped in nixpkgs.
The Home Manager module allows us to customize the different vim options. To use it, we first add the input flake.
{
neovim-flake = {
url = github:notashelf/neovim-flake;
# you can override input nixpkgs
@@ -91,7 +94,7 @@ These options are attribute sets, and you need to give the configuration you’r
};
};
};
-}Language specific support means there is a combination of language specific plugins, treesitter support, nvim-lspconfig language servers, and null-ls integration. This gets you capabilities ranging from autocompletion to formatting to diagnostics. The following languages have sections under the vim.languages attribute. See the configuration docs for details.
Language specific support means there is a combination of language specific plugins, treesitter support, nvim-lspconfig language servers, and null-ls integration. This gets you capabilities ranging from autocompletion to formatting to diagnostics. The following languages have sections under the vim.languages attribute. See the configuration docs for details.
vim.languages.rust.enable
vim.languages.nix.enable
diff --git a/options.html b/options.html
index 56b8a870..de558dce 100644
--- a/options.html
+++ b/options.html
@@ -28,6 +28,8 @@ the nixpkgs.pkgs option.Whether to enable experimental Lua module loader to speed up the start up process. Type: boolean Default: Example: Declared by: The neovim package to use. You will need to use an unwrapped package for this option to work as intended. Type: package Default: Declared by: Whether to enable GitHub Copilot AI assistant. Type: boolean Default: Example: Declared by: Whether to enable nvim-cmp integration for GitHub Copilot. Type: boolean Default: Example: Declared by:vim.enableLuaLoaderfalsetrue
<neovim-flake/modules/basic/module.nix>
+ vim.package<derivation neovim-unwrapped-0.9.1>
+ <neovim-flake/modules/basic/module.nix>
vim.assistant.copilot.enablefalsetrue
<neovim-flake/modules/assistant/copilot/copilot.nix>
vim.assistant.copilot.cmp.enablefalsetrue