nvf/docs/manual/custom-package.md

# Custom Neovim Package {#ch-custom-package}

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.

```nix
{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.
docs: refactor 2023-12-09 19:03:58 +00:00			`# Custom Neovim Package {#ch-custom-package}`
docs: document custom package usage 2023-08-02 06:53:07 +00:00
			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.

docs: refactor 2023-12-09 19:03:58 +00:00			```nix
docs: document custom package usage 2023-08-02 06:53:07 +00:00			`{inputs, pkgs, ...}: {`
			`# using the neovim-nightly overlay`
			`config.vim.package = inputs.neovim-overlay.packages.${pkgs.system}.neovim;`
			`}`
docs: refactor 2023-12-09 19:03:58 +00:00			```
docs: document custom package usage 2023-08-02 06:53:07 +00:00
			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.