Allow more modular plugin configuration

[jdsee]

Hi 👋 first of all, thanks for all the work on this cool project!

When trying to port my Lua config to Nixvim I stumbled over a couple of things. Adding extra Lua Code for specific plugins bothered me the most.

In my Lua config I like to have one file per plugin and try to contain everything related in that one file. I see the following advantages in that approach:

• easy to find and edit
• code can be excluded easily when plugin is disabled or lazy loaded
• removing a plugin would simply mean to remove that one file

I tried to replicate this style with Nixvim (one module per plugin) but struggled with custom Lua code for specific plugins. I would like to avoid squeezing all the plugin specific code in extraConfigLua for the previously stated reasons.

Personally I would really like, if every plugin had extraConfigLua as a default key. That Lua code should then only be included if the plugin is enabled. The same approach would be really helpful for extraPlugins since those don't have any options declared.

Another fortunate side effect would be the simplification of the (potentially) upcoming lazy loading. If I'm not mistaken currently it would lead to problems if a lazily loaded plugin was required from extraConfigLua.

So I'm wondering, if others can relate to this issue or if I'm just missing out on something. Anyone an opinion on this?

[siph]

I may have misunderstood something but you can have multiple extraConfigLua values declared. It doesn't help with eventual lazy-loading but you can keep the relevant parts in one file.

[traxys]

Yeah NixOS modules are really powerful! You can do lot's of quite advanced stuff with them (this is how nixvim is implemented too!).

[jdsee]

It’s really great. Most of my setup is configured with Nix but I’m still getting confused sometimes. Thanks for shedding some light on the mkIf :)

I’m really excited about Nixvim. Just missing the lazy loading (and with that the ability to declare dependencies between the modules).

Another (slightly unrelated) thing that confused me was the incoherent definition of keymaps in different plugins. Would it be helpful if I wrote an issue for unifying the keymap schemas between all plugins?

[traxys]

Dependencies should be managed automatically by nixpkgs itself (and for some plugins nixvim).

Unifying keymaps (introduced by nixvim directly, not a plugin option) is a future goal yes.

[alexandru0-dev]

@traxys is there a way to get the config argument as a recursive reference when using in combination with makeNixvimWithModule? (so flake with nixvim config)

[MattSturgeon]

Not sure what you mean by "recursive reference", but you can have access to the evaluated/merged config both within the nixvim modules (as a module arg) and on the resulting derivation (as an additional attribute).

let
  myNvim = makeNixvim (
    { config, options, lib, pkgs, ... }: {
      # Can access `config` as a module arg here
    }
  );

  # Or as an attr on the derivation:
  myConfig = myNixvim.config;
in

[GaetanLepage]

@jdsee has your question found a satisfying answer ?

[jdsee]

Thanks for catching up. I moved away from nixvim in favor of a simple lua config. I think this comment is probably the closest thing to what I was looking for at that time.

[khaneliman]

Now we have ‘plugins..luaConfig.<pre|post|content>’ which is more ergonomic