Dogfooding home-manager configuration

[TakodaS]

Hi, so I figured out how to re-use my extensively set up helix home-manager configuration for yazelix. I wanted to take advantage of all the integrations within yazelix (i.e. to be warned if I override a yazelix keybinding), which would not be possibile if I used my helix as an external editor.

programs.yazelix =  let
        tomlFormat = pkgs.formats.toml { };
        helix = config.programs.helix;
  in
{
          enable = true;
          config = {
            helix = {
              config.source = tomlFormat.generate "yazelix-helix-config.toml" helix.settings;
              languages.source = tomlFormat.generate "yazelix-helix-languages.toml" helix.languages;
            };
            settings = {
              welcome.enabled = false;
            };
          };
        };

Thank you @luccahuguet for such an amazing project!

[luccahuguet]

awesome! thnkss

[luccahuguet]

spread the word ❤️

[luccahuguet]

Thanks for sharing this pattern. It is now documented in the Home Manager installation guide and covered by the module check so both generated files must land under ~/.config/yazelix/helix/.

One boundary: this reuses settings and languages, but it does not carry over extraConfig, custom themes, ignores, or the PATH from extraPackages. Do you depend on any of those in your setup? Repeated demand should come before a first-class bridge for them.