-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declared neovim plugin seemingly not installed #815
Comments
I had to open a new terminal for changes to apply, apparently. Help file is now accesisble via |
@Gerschtli You seem to know about VIM. Do you have any idea what's going on here? |
How did you executed neovim in your first try before opening a new terminal? Because the destination path to the I can reproduce that |
Derp. Perhaps this is related to Though, I'm currently using the new |
What do you mean with getting really angry? |
I'll post the error messages once I'm at work. It spits out a bunch of them. |
Here's what I meant by |
On first sight it seems to me that not all vim config files get correctly sourced.. Did you get it working sometime before? |
I also wonder if this might be related to |
Interesting.. Maybe you can find the commit in home-manager and/or nixpkgs where rust-vim stopped working correctly in neovim. That would be my approach to find the error. |
Ahhh @Gerschtli was on the right track. It was indeed a simple setting on my end. I just had to set Oddly enough, |
Ah perfect!
|
Ah, that's correct, it does not. |
Sorry for only giving instruction, but I don't get to my computer until next week and I don't have much time right now.. Thank you very much for your time and efforts! :) Could you look, where the |
Pretty sure it's just |
The problem is the loading order (see for a similar issue lervag/vimtex#695). In position 23 (see log below) the builtin ftplugin for tex is loaded. It seems to be an issue in the nixpkgs expression of neovim (and vim as well).. I have to investigate further. My expression so far: {
programs.neovim.enable = true;
programs.neovim.plugins = [ pkgs.vimPlugins.vimtex ];
} Output of
|
This is extremely reassuring if it is simply something in the neovim expression, as I was starting to see multiple packages that were affected. |
If you have some valuable input for NixOS/nixpkgs#69373, you can comment it there :) |
This can probably be closed, since its not a home-manager issue. Its a dupe of NixOS/nixpkgs#39364 which I've already reported upstream some while ago. Dupes keep popping up, but I don't know what to do about it. Would be great if someone had some spare time and could look into the upstream issue (neovim/neovim#9390). |
Here's my current workaround for anybody interested, based on this comment. |
Interesting, we could probably add something like that to the default plugin handling. Not sure if there would be any negative side-effects though. I'd much prefer it if this could be handled upstream. |
this might be solved by NixOS/nixpkgs#78385 |
closing as a non home-manager issue |
In the processing of configuring everything with Nix I'm currently porting my neovim configuration. With the following:
I expect
:h vimtex
to open the plugin's help file, as is the case if the plugin is installed with vim-plugged, but the file cannot be found. Am I missing something in the declaration?Cheers.
The text was updated successfully, but these errors were encountered: