Introduce

The KISS-based configuration that maximizes the use of Neovim's built-in functionality.

How my configuration might be useful to you?

Fuck status lines. Current branch/commit in `:h 'ruler'`

I don't like all those overloaded status lines, so I just wrote this simple branch/commit tracker for use in options like :h 'rulerformat'.

If you want the same copy ruler.lua to your config and configure the options according to your preferences at the bottom of the file. By default it will look like a standard ruler, but with branch/commit displayed, and will also disable the status bar.

Yes, now you can't see file names, you can use :h 'winbar' for that:

vim.opt.winbar = '%#Normal# %<%=%(%* %y%f%m%r%) '

I use it with a plugin like SmiteshP/nvim-navic to get the context on the left side of the winbar and the file name on the right.

Nix overlay/wrapper for configuring package content

Did he write another way to configure Neovim with nix?

No, I don't like all the things people are doing with Neovim using Nix. In my opinion it just makes your user experience more complicated and uncomfortable. Try to answer the following questions:

What's the point of keeping your configuration in immutable store and losing the ability to make quick changes?
We already have a first class supported language in Neovim to write our configuration with all that lsp stuff, syntax highlighting, etc. So why give it up?
Any plugin, has instructions on how to install it easily by copying a snippet from the README. Is it really that much harder than enabling the option in Nix?
Neovim already has a very cool plugin manager with lazy loading, lock file and bytecode compilation. As far as I know the latter is not available in any Nix solution. So, what benefits will you get from Nix?

But I also want to have an easily portable Neovim configuration. So that on any machine that has Nix installed, I can quickly get into my development environment. That's why I wrote this. My overlay allows you to define a Neovim package with a number of dependencies, which also contains a small script to bootstrap your Neovim configuration from git repo at startup.

Unlike the solutions I know:

The NixOS module in nixpkgs
The module in Home Manager
nixvim
neovim-flake

My overlay does not involve configuring Neovim with Nix. Instead, it enables you to wrap the standard neovim-unwrapped package using the standard wrapper provided in nixpkgs. This allows you to configure the following aspects:

Add packages to $PATH, specifically for Neovim.
Add Tree-sitter parsers via package rebuild or :h 'rtp' option.
Add additional Lua code to pre-init.lua.
Add additional arguments to makeWrapper.

Note. Here is a list of nvim-treesitter parsers that will be added anyway:

c
lua
vim
vimdoc
query
python
bash
markdown
markdown_inline

The reason is that the bundled Neovim parsers may be out of date for nvim-treesitter and cause errors.

nvim-treesitter/nvim-treesitter#5873

:h treesitter-parsers to get list of the bundled parsers

What is `pre-init.lua`?

This is a Lua file that is executed with the command --cmd "luafile pre-init.lua", which means that it is executed before any vimrc is processed. It consists of:

vim.g.is_nix_package = 1. This can be used to change the configuration based on whether Neovim is a package from this overlay.
If rebuildWithTSParsers is false, which is the default behavior, it adds nvim-treesitter parsers to the 'runtimepath' option and sets the nix_ts_parsers global variable that stores the path to the parsers. This global variable can be used to redefine the 'runtimepath' option. So, for example, by default Lazy.nvim resets the 'runtimepath' option.
If repo is not null, it also contains a snippet that checks and clones the repository from the specified URL. See the repo argument below.
Any additional Lua code you specify with additionalPreInit.

Arguments for override

Arguments that are simply passed to neovimUtils.makeNeovimConfig. Source:

extraName, string, default: "". The suffix to be added to the name attribute in the derivation.
viAlias, bool, default: false. Similar to the programs.neovim.viAlias option in NixOS.
vimAlias, bool, default: false. Similar to the programs.neovim.vimAlias option in NixOS.
withPython3, bool, default: false. Similar to the programs.neovim.withPython3 option in NixOS.
withNodeJs, bool, default: false. Similar to the programs.neovim.withNodeJs option in NixOS.
withRuby, bool, default: false. Similar to the programs.neovim.withRuby option in NixOS.
withPerl, bool, default: false. Similar to the above options enable the Perl provider. But this is still an experimental option, be careful.
extraPython3Packages, default: _: [ ]. A function that you normally pass in python.withPackages, but which is passed to the python provider Neovim.
extraLuaPackages, default: _: [ ]. Similar to the above.

Additional arguments, that implemented inside wrapper.nix:

repo, string or null, default: null. On startup, Nvim will check if the specified repository is a user configuration, and load it if it is not. If some configuration already exists but is not the specified repository, it will be renamed with the prefix "_backup_{current date}". The git remote get-url origin command is used for verification.
additionalPreInit, string, default: "". Any Lua code you want to add to pre-init.lua. Be careful, it will be executed every time you open Neovim.
additionalWrapperArgs, list of string, default: [ ]. As mentioned above, using this option you can add arguments to makeWrapper.
extraBinPath, list of package, default: [ ]. Packages to be added to $PATH.
extraTSParsers, package list, default: [ ]. Tree parsers to be added to 'rtp' and to the nix_ts_parsers global variable or to $out/lib/nvim/parser/ if rebuildWithTSParsers is enabled.
rebuildWithTSParsers, bool, default: false. Whether Tree-sitter parsers should be added via the 'runtimepath' option or by overriding the preConfigure phase in the neovim-unwrapped derivation. Rebuild is the more general and recommended approach, so if you are using the nightly version and already rebuild neovim-unwrapped, it is recommended to enable this option.

Usage example

If you use flakes

# flake.nix
{
  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    # Add input
    nvim.url = "github:name-snrl/nvim";
  };

  outputs = { self, nixpkgs, ... }@inputs: {
    nixosConfigurations.<hostname> = nixpkgs.lib.nixosSystem {
      modules = [ ./configuration.nix ];
      # pass inputs to config
      specialArgs = { inherit inputs; };
    };
  };
}

# configuration.nix
{ pkgs, inputs, ... }: {
  nixpkgs.overlays = [
    # Add my overlay. It uses final.callPackage, so it doesn't matter the
    # sequence in which it is added, it will always use neovim-unwrapped from
    # the final package set.
    inputs.snrl-cfg.overlays.default
    # configure your own package
    (final: prev: {
      my-nvim = final.nvim.override {
        viAlias = true;
        vimAlias = true;
        repo = "https://github.com/<user-name>/<repo>";
        extraBinPath = with final; [
          curl
          fd
          ripgrep
        ];
        extraTSParsers = with final.vimPlugins.nvim-treesitter-parsers; [
          fish
          go
          rust
          css
          yaml
          dockerfile
        ];
      };
    })
  ];
  # add it to environment.systemPackages or wherever you want
  environment.systemPackages = with pkgs; [
    my-nvim
  ];
}

If you use channels

This solution will work with any type of configuration, but you will have to update the commit hash and the fetchFromGitHub hash yourself.

# configuration.nix
{ pkgs, inputs, ... }: {
  nixpkgs.overlays = [
    (final: prev: {
      my-nvim =
        let
          nvim-overlay = prev.fetchFromGitHub {
            owner = "name-snrl";
            repo = "nvim";
            # This will work, but will probably be out date.
            #
            # To update, replace `rev` with the latest repository commit,
            # set `hash` to the empty string, run the build. Nix will throw
            # an error with the correct hash, replace the empty string with it.
            #rev = "f3e632ac63c24fa82c3ac09e7f7a0c7962c012bd";
            #hash = "sha256-9OgP1e8d3O6W0F0tQe+BdGYghNKpFPjStajFnqp4z4k=";
          };
        in
        final.callPackage "${nvim-overlay}/wrapper.nix" {
          # your overrides here
        };
    })
  ];
  # add it to environment.systemPackages or wherever you want
  environment.systemPackages = with pkgs; [
    my-nvim
  ];
}

FAQ

What wrapping is?

This is creating a small bash script around the package to create its own environment. As you may have noticed, nixpkgs has many packages with the suffix -unwrapped, which means that it is a standardly built package with standard output. But sometimes a wrapper is created for a package to work properly in NixOS or to customize it through a module, so wrapped packages are hidden under their normal names. What does a wrapper look like? Execute:

nvim "$(realpath "$(which nvim)")"

Is this causing Neovim to be rebuilt?

No, unless the rebuildWithTSParsers option is enabled. By default, this just builds a thin bash wrapper around the neovim-unwrapped package.

How do I change the package that will be wrapped?

By default, the overlay uses your system's neovim-unwrapped package from the final argument, which means that if you use neovim-nightly, which overrides the neovim-unwrapped package, you don't need to do anything. Or you can specify the package manually via override:

final: prev: {
  my-nvim = final.nvim.override { neovim-unwrapped = prev.neovim-i-want-wrap; }
}

Plugins I use

git integration
- vim-fugitive

DanMax03/my-nvim-fork

Introduce

How my configuration might be useful to you?

Fuck status lines. Current branch/commit in `:h 'ruler'`

Nix overlay/wrapper for configuring package content

What is `pre-init.lua`?

Arguments for override

Usage example

If you use flakes

If you use channels

FAQ

What wrapping is?

Is this causing Neovim to be rebuilt?

How do I change the package that will be wrapped?

Plugins I use

TODO

DanMax03/my-nvim-fork

Introduce

How my configuration might be useful to you?

Fuck status lines. Current branch/commit in :h 'ruler'

Nix overlay/wrapper for configuring package content

What is pre-init.lua?

Arguments for override

Usage example

If you use flakes

If you use channels

FAQ

What wrapping is?

Is this causing Neovim to be rebuilt?

How do I change the package that will be wrapped?

Plugins I use

TODO

Fuck status lines. Current branch/commit in `:h 'ruler'`

What is `pre-init.lua`?