Closed ghost closed 2 years ago
So I'm not crazy. This is also happening to me, also running 21.11.
programs.neovim = {
enable = true;
extraConfig = ''
luafile "/home/mixedcase/.config/nvim/init.lua";
'';
};
results in this .config/nvim/init.vim
:
" configuration generated by NIX
set nocompatible
set packpath^=/nix/store/kkfrhcjnwx7170iyqmf7rp0rycf8xhj1-vim-pack-dir
set runtimepath^=/nix/store/kkfrhcjnwx7170iyqmf7rp0rycf8xhj1-vim-pack-dir
luafile "/home/mixedcase/.config/init.lua";
luafile "/home/mixedcase/.config/init.lua";
@yourfavouriteuncle For whatever it's worth, I just realized I could workaround this with relative ease, hope it helps in the meantime:
extraConfig = ''
if !exists("homemanagerbug")
let homemanagerbug = "yes"
luafile /home/mixedcase/.config/nvim/init.lua
endif
'';
cc: @teto
the following patch should fix it.
diff --git a/modules/programs/neovim.nix b/modules/programs/neovim.nix
index c63f04e1..12377ab4 100644
--- a/modules/programs/neovim.nix
+++ b/modules/programs/neovim.nix
@@ -51,7 +51,7 @@ let
(map (x: if x ? plugin && x.optional == true then x.plugin else null)
cfg.plugins);
};
- customRC = pkgs.lib.concatMapStrings pluginConfig cfg.plugins + cfg.extraConfig;
+ # customRC = pkgs.lib.concatMapStrings pluginConfig cfg.plugins + cfg.extraConfig;
};
extraMakeWrapperArgs = lib.optionalString (cfg.extraPackages != [ ])
Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.
Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Still valid as of 7d9ba15214004c979d2c8733f8be12ce6502cf8a
(latest commit for release-21.05)
@mixedCase does the above snippet work for you ?
No idea how to apply your patch without a lot of work to tell you the truth. I get home-manager with fetchGit like this:
home-manager = builtins.fetchGit {
url = "https://github.com/nix-community/home-manager.git";
rev = "7d9ba15214004c979d2c8733f8be12ce6502cf8a";
ref = "release-21.05";
};
How can I apply your patch on top without making a whole 'nother repo?
I think the best it to fork the project, then patch it . You dont have to necessarily push the changes to your fork, you can reference a local clone. This way you are ready next time you want to contribute ;)
Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.
Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
This is still relevant.
I don't know what happened in the last 3 months but I can no longer reproduce this using rev a8d00f5c038cf7ec54e7dac9c57b171c1217f008
Seems fixed to me!
I'm going to close then. If you run into it again, we can reopen.
Issue description
I'm on nixos unstable, updated today.
I noticed that my startup time is longer than I'm used to. I run vim with
startuptime
to troubleshoot. I see many duplicated entries.I see that in my configuration I have duplicated entries:
Technical details
$ nix-shell -p nix-info --run "nix-info -m" these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/lp90qhw19dcp79cnlicjg09llgh7dzsz-bash-interactive-4.4-p23-dev copying path '/nix/store/lp90qhw19dcp79cnlicjg09llgh7dzsz-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
"x86_64-linux"
Linux 5.10.44, NixOS, 21.11pre296557.33d42ad7cf2 (Porcupine)
yes
yes
nix-env (Nix) 2.3.12
"nixos-21.11pre296557.33d42ad7cf2, home-manager"
""
/nix/var/nix/profiles/per-user/root/channels/nixos