-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
vim and plugin managing #4569
Comments
I've done smth like jagajaga@91d97be |
@jagajaga: I didn't know our vim-plugins aren't fully loading. (I'm still using VAM, although I'm thinking of switching to vim-plugins from nixpkgs.) Is it just stuff in "after/" that's not loading? What does pathogen do to load plugins? I'm sure pathogen has more features than just loading plugins (I mean, it fetches and "builds" plugins too, right?). Maybe we could just take a look at its "loading code" and copy (parts of) it? |
@bjornfor no, pathogen is a tool, which just load a plugin (or plugins from directory). That's why I'm suggesting it. |
@jagajaga: Ok, sounds like a good idea to use pathogen then. |
@bjornfor nice, I will make it and PR then. |
Now we can load system plugins to vim.
But the bug we have is that the
after
folder from plugins isn't loaded.Yeah, we can improve the current configuration https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/vim/configurable.nix#L11 etc, but everytime we can get bugs anyway.
I think it's a good idea to make tpope/vim-pathogen as a mandatory plugin for vim and load everything with it (just as build helper).
The idea is not to make people use pathogen, the idea is to load plugins from the
configuration.nix
and give it to users. Then they can manually install pathogen and use it if they need. We won't provide it to the userspace.The text was updated successfully, but these errors were encountered: