Luc Chabassier

I'm sorry, I haven't taken the time yet to do it. I'll try to do it before the end of july.

Any news on that front ? I'd be very interested by a way to specify injectivity on some arguments only.

I have the same error, and when trying to use the legacy method, it complains that it finds the `Flags` module twice, once in `coq-core/lib` and once in ocaml `core_kernel/flags`,...

I have a working package [there](https://github.com/dwarfmaster/home-nix/blob/master/packages/fvim/default.nix). I may consider opening a PR on nixpkgs, but there are a few things I am unsatisfied with, mainly that I have to patch...

Oh right you need to escape the #, ie `nix run "github:dwarfmaster/home-nix#fvim"` (I think, for some reason even without the quotes it works on my computer).

I feel like this issue should stay open until it is fixed, if only to have a point of reference when encountering this issue. While I agree the doom CLI...

> > If you're using an official base16 theme, you can do : > > ```nix > > { config, lib, ... }: > > { > > programs.nixvim =...

Another problem with your solution is that it disable cursorline highlighting, instead of resetting it to its previous value. A solution could be to store the highlight setting for CurrsorLine...

It may make sense to include the `themeFile` option for the modules where we generate it ourselves, but for the wezterm module we use the home-manager module to set the...

For your specific situation I can think of two solutions: - Add `xdg.configFile."wezterm/wezterm.lua".enable = lib.mkForce false` to disable the generation of the wezterm.lua file while still enabling wezterm in home-manager...