modules/output: Remove the initContent option

This (internal) option introduces IFD, and can be substituted internally
with the `initPath` option easily.
If the content is required somewhere users can use readFile on the
initPath, though it will result in an IFD in their project.
This commit is contained in:
traxys 2024-07-05 22:08:25 +02:00
parent 8fbcfcb469
commit 367380bd84
3 changed files with 2 additions and 10 deletions

View file

@ -61,13 +61,6 @@ with lib;
visible = false;
};
initContent = mkOption {
type = types.str;
description = "The content of the `init.lua` file.";
readOnly = true;
visible = false;
};
printInitPackage = mkOption {
type = types.package;
description = "A tool to show the content of the generated `init.lua` file.";
@ -142,7 +135,6 @@ with lib;
{
type = lib.mkForce "lua";
finalPackage = wrappedNeovim;
initContent = readFile init;
initPath = "${init}";
printInitPackage = pkgs.writeShellApplication {

View file

@ -18,7 +18,7 @@ let
shared = import ./_shared.nix helpers args;
cfg = config.programs.nixvim;
files = shared.configFiles // {
"nvim/init.lua".text = cfg.initContent;
"nvim/init.lua".source = cfg.initPath;
};
in
{

View file

@ -19,7 +19,7 @@ let
shared = import ./_shared.nix helpers args;
cfg = config.programs.nixvim;
files = shared.configFiles // {
"nvim/sysinit.lua".text = cfg.initContent;
"nvim/sysinit.lua".source = cfg.initPath;
};
in
{