nixos-config VS neovim-nightly-overlay

If you use home-manager, installing starship is as simple as adding `programs.starship.enable = true;`.

https://github.com/srid/nixos-config/blob/master/home/starsh...

Incidentally, starship also gives a visual indication of whether you are in the nix shell or not, which is pretty handy when using direnv:

https://nixos.asia/en/direnv

In https://github.com/srid/nixos-config I share home-manager modules (everything under ./home/ basically) between NixOS and macOS.

Don't use nix build to build neovim. Add an overlay to your flake and use home-manager programs.neovim option. It will automatically compile latest neovim for you when you rebuild the configuration.

Relevant? https://github.com/nix-community/neovim-nightly-overlay/issues/164

You can use the overlay

You can use the nix-community overlay or the flake.

-- SNIP -- nixpkgs.overlays = [ (import (builtins.fetchTarball { url = https://github.com/nix-community/neovim-nightly-overlay/archive/master.tar.gz; })) ]; -- SNIP -- programs = { neovim = { enable = true; package = pkgs.neovim-nightly; configure = { customRC = (builtins.readFile ./init.vim); }; }; }; -- SNIP --

There is no centralised way of sharing user packages. But you can create package overlays or use sombodys overlays if you can find them (e.g. I use neovim nightly overlay).

However, then you run into this issue.

Ok so I am using https://github.com/nix-community/neovim-nightly-overlay to build neovim from source in order to use the latest features. Does anyone know of any way I can specify makeflags, such as march=native or O3 when building the package? Thanks so much for your help.

I'm using https://github.com/nix-community/neovim-nightly-overlay which does get Neovim 0.5 running, it's just not using my init.lua properly, picking up its own init.vim instead.