EDIT: Nevermind seems I didn’t read the docs/source clearly enough heh.
Query, any thoughts on adding options to alias vim/via to nvim in the hm module? The default nvim module already does this and it’d be handy to do so with your flake as well.
Around two years ago, when I started getting into Nix, I decided I needed a way to configure Neovim using it. At the time, I couldn’t find anything that did what I wanted, so I created NixVim! It’s a set of Nix modules, usable through either NixOS or Home Manager that allows you to declaratively configure Neovim.
It’s proved extremely useful several times now, as it made porting my config completely effortless.
Have been looking around for a good way to configure Neovim with Nix and found most of them wanting, glad I found this a week ago and told all my friends. Thanks for your work and I hope the project thrives!
If you’re just going to call eachSystem, you don’t need to add a dependency of flake-utils. This makes downstream users download an extra dependency too—it’s one line of Nix to write this which would actually remove the number of line in the file. There’s also a couple philosophical issue as well: if you’re not testing ARM Linux, should you be saying you support it? Should you be supporting flake-util’s 4 ‘default’ architectures when that doesn’t match those listed in pkgs.neovim.meta (32-bit Linux is supported for Hydra builds, but this project doesn’t?)
That’s a fair argument. As far as unsupported architectures go, I wouldn’t really want to explicitly want to remove support for any (by not listing it), I’d rather just say that’s officially supported on arm64 and x86_64 Linux as that’s what I can test, but everything else is available in a “you’re on your own” basis.
EDIT: Nevermind seems I didn’t read the docs/source clearly enough heh.
Query, any thoughts on adding options to alias vim/via to nvim in the hm module? The default nvim module already does this and it’d be handy to do so with your flake as well.
Around two years ago, when I started getting into Nix, I decided I needed a way to configure Neovim using it. At the time, I couldn’t find anything that did what I wanted, so I created NixVim! It’s a set of Nix modules, usable through either NixOS or Home Manager that allows you to declaratively configure Neovim.
It’s proved extremely useful several times now, as it made porting my config completely effortless.
Have been looking around for a good way to configure Neovim with Nix and found most of them wanting, glad I found this a week ago and told all my friends. Thanks for your work and I hope the project thrives!
Thank you! Nice to know there are actual users :) A lot of the credit lately goes to the other contributers too!
If you’re just going to call eachSystem, you don’t need to add a dependency of flake-utils. This makes downstream users download an extra dependency too—it’s one line of Nix to write this which would actually remove the number of line in the file. There’s also a couple philosophical issue as well: if you’re not testing ARM Linux, should you be saying you support it? Should you be supporting flake-util’s 4 ‘default’ architectures when that doesn’t match those listed in pkgs.neovim.meta (32-bit Linux is supported for Hydra builds, but this project doesn’t?)
That’s a fair argument. As far as unsupported architectures go, I wouldn’t really want to explicitly want to remove support for any (by not listing it), I’d rather just say that’s officially supported on arm64 and x86_64 Linux as that’s what I can test, but everything else is available in a “you’re on your own” basis.
But if that’s you philosophy, then why skip the i686 arch that Hydra supports?
Because I set this up two years ago when I was a Nix noob and didn’t know that, so I’ll update it to add the extra architectures.