Pedro Alves

Hey, finally have time to work on this, can you show me what your config looks like? Because I've not had this issue myself.

Seems like it! As part of my work with #16, this should get fixed soon, since I am effectively redoing the whole non-HM setup from scratch.

For now, I'd recomend using the `standalone` branch, and not using the NixOS module, instead using the build function and putting it on `environment.systemPackages`: ```nix { environment.systemPackages = [ #...

> As a side question, is it possible to use nix-colors to create a colorscheme in nixvim? There isn't any nix-colors module right now, but I can add one. If...

This is a good idea, I think the best way to go about it would be to add an extraOptions or similar to all Lua modules. Shouldn't be hard to...

I'll be home next week and will be able to work on this. In the meantime, feel free to come up with something!

This seems to only happen on `nixos-22.05`, but honestly I can't really figure out why... Maybe it's related to #44 and it didn't end up being a full fix, will...

Was just thinking about the template! I can probably take care of that tomorrow though, no need to worry about it :)

I think the best-case scenario for this would be something like ```nix { ft."nix" = { plugins.nix.enable = true; options.numbers = true; }; } ``` as in, allowing the full...

I'm not really sure how desirable it can be to fix this, I think the alternative fix to preserve backwards-compatibility would be to just run everything in a lua block...