nix-community/nixvim
1
0
Fork 0
mirror of https://github.com/nix-community/nixvim.git synced 2025-12-09 10:31:08 +01:00
Code Activity

treewide: NixVim/nixvim -> Nixvim

Browse source 
Signed-off-by: saygo-png <saygo.mail@proton.me>
This commit is contained in:
saygo-png 2025-12-04 16:36:05 +01:00 • committed by Matt Sturgeon
parent 5d1c27e53c
commit 03a51dbf3d
34 changed files with 78 additions and 78 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/user-guide/faq.md
View file

@ -7,7 +7,7 @@ Using a plugin not supported by nixvim, but packaged in nixpkgs is straightforwa
- Register the plugin through `extraPlugins`: `extraPlugins = [pkgs.vimPlugins."<plugin name>"]`.
- Configure the plugin through `extraConfigLua`: `extraConfigLua = "require('my-plugin').setup({foo = "bar"})";`
## How do I use a plugin not yet merged into NixVim or temporarily modify one
## How do I use a plugin not yet merged into Nixvim or temporarily modify one
Copy the module expression formatted like this into a file:
@ -18,7 +18,7 @@ lib.nixvim.plugins.mkNeovimPlugin {
}
```
Import it into your NixVim configuration and configure it:
Import it into your Nixvim configuration and configure it:
```nix
{
# Remove this `programs.nixvim` wrapper for standalone configurations
@ -84,13 +84,13 @@ When using Nixvim, it is possible to encounter errors about something not being
```
This usually means one of two things:
- The nixpkgs version is not in line with NixVim (for example nixpkgs nixos-25.11 is used with NixVim master)
- The nixpkgs unstable version used with NixVim is not recent enough.
- The nixpkgs version is not in line with Nixvim (for example nixpkgs nixos-25.11 is used with Nixvim master)
- The nixpkgs unstable version used with Nixvim is not recent enough.
When building nixvim using flakes and our ["standalone mode"][standalone], we usually recommend _not_ declaring a "follows" for `inputs.nixvim`.
This is so that nixvim is built against the same nixpkgs revision we're using in our test suite.
When building Nixvim using flakes and our ["standalone mode"][standalone], we usually recommend _not_ declaring a "follows" for `inputs.nixvim`.
This is so that Nixvim is built against the same nixpkgs revision we're using in our test suite.
If you are building nixvim using the NixOS, Home Manager, or nix-darwin modules then we advise that you keep your nixpkgs lock as close as possible to ours.
If you are building Nixvim using the NixOS, Home Manager, or nix-darwin modules then we advise that you keep your nixpkgs lock as close as possible to ours.
> [!TIP]
> Once [#1784](https://github.com/nix-community/nixvim/issues/1784) is implemented, there will be alternative ways to achieve this using the module system.
@ -139,7 +139,7 @@ keymaps = [
[`map`]: https://nixos.org/manual/nix/stable/language/builtins#builtins-map
[`keymaps`]: ../keymaps
## How to use system provided binaries instead of nixvim provided ones
## How to use system provided binaries instead of Nixvim provided ones
There are a number of plugins that install extra packages using `nix`, but this can cause issues.
For example enabling `plugins.treesitter` could add `gcc` to the PATH of neovim, and this could break workflows that rely on the system provided compiler.