Config Share Megathread

[BirdeeHub]

If you are so inclined, want advice, or made something cool, here is the place to show off what you have done with nixCats!

[BirdeeHub]

To get the thread started:

Mine is a mess, but its my mess.

I do not guarantee that everything in it works.

This is not a distro, its the graveyard of plugins I might have never fully set up. If something is broken get your own config XD (sorry kotlin/java/sorta python)

While I would not suggest using my config, I definitely have a lot of stuff in it and it works for what I need it for, and lze keeps it loading fast despite my plugin addiction!

[BirdeeHub]

and, honorable mention from this thread on stylix there is bbaserdem's config which is somewhat newly created but I think is neat because the nix template has been factored out nicely, and it makes use of the new lsp directory that the example config is not on a new enough version of nvim to use yet, and wrote an lze handler to automate some things he does often.

[dwinkler1]

I'm quite new to nix so happy to take any suggestions for improvements. My config is based on the example template and I added a few things I was using with LazyVim before. The trickiest part was adding the extension for R and I suspect it won't work on NixOS because it installs its own R package into a user directory. This could possibly be solved with an overlay? I'm using Nix on Darwin / Linux Mint so I can't test on NixOS easily. Hope it inspires others:

https://github.com/dwinkler1/nixCatsConfig

[BirdeeHub]

because it installs its own R package into a user directory

I mean, that might actually be fine even on nixos tbh?

I see you are doing the rWrapper.override thing

So, one would hope that anything that it does pull to a user directory, will already have its dependencies taken care of by rWrapper from nix? In which case that would be fine.

So, yeah, idk, I have never used R personally but that would be my assumption is that the offered wrapper would be sufficient to install the things installed via said wrapper.

And, an overlay might not be the thing that fixes that necessarily, unless you would like to change what rWrapper points to.

But you could definitely use overrideAttrs to modify the derivation further and add stuff that is missing if it doesnt work,.

And you could then decide to use a overlay for that modification, so that your modified version replaces pkgs.rWrapper with your modified rWrapper derivation rather than doing it directly in your lspsAndRuntimeDeps list.

My guess would be that it should just work the way you have done it there though on nixos

[dwinkler1]

Thank you for the insights and all the good work on nixCats! It's really a great experience using Neovim.
I've used R for many years and this is the first time I'm seeing this construct with an external program installing its own R package that is not upstreamed so I'm not sure what is happening in the background but it insisted to install to /Users/daniel/Library/R/arm64/4.5/library/nvimcom there is an issue in their repo talking about the nix overlay R-nvim/R.nvim#229 (comment) but I'm happy that it works as it does for now. As an aside nix is getting quite popular with the R community due to the work done in rix and I'm working on contributing a flakes based version. In the medium run I'd like to showcase that with a setup combining nixCats + latest R but that will still take a while for me to figure out. My dream is essentially a dev flake that pulls down everything needed to work on a project with R + Neovim setup.

[dwinkler1]

You are right, the R package should just work according to the wiki (this is for a previous version of the package but should be similar enough). Just requires gcc. Would I add that to LspAndRuntimeDeps if I don’t want to rely on system packages?

[BirdeeHub]

Yes. lspsAndRuntimeDeps adds to PATH, and that should be all that is required

If you have some c libraries that need to be accessed via ffi, sharedLibraries adds to LD_LIBRARY_PATH for that, analogous to an nvim-local nix-ld. But this is rarely needed, usually path is enough

[BirdeeHub]

also, for your choice of c compiler, if it lets you use a couple different c compilers, go for pkgs.stdenv.cc.cc instead of the gcc package directly so that you dont end up with 2 c compilers for no reason, but it doesnt matter much