You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see I suggested to do something like this : map \u call pathogen#infect() to rescan the bundles directory.
Maybe you could provides a default mapping for this and mention somehting in the documentation ? Unless
this happens to be a bad idea for some reason ?
The text was updated successfully, but these errors were encountered:
I've wanted something like this for a while. Two big caveats:
Calling pathogen#infect() a second time results in scanning not just the original runtime path, but also inside any bundles that were added the previous go around. With a lot of bundles, this is noticeably slow. Plus the path ends up in a weird order.
If Vim has already loaded, we need to manually activate plugins and filetype detection. This is not necessarily unfeasible, but I'm guessing there are edge cases hiding in there (things like Using pathogen breaks detecting git commits #38).
@tpope have you thought a bit more regarding this? I'm currently using pathogen for my standalone plugin manager and it would be awesome not having to close the editor when you install a new plugin.
This is more of a request than a bug. I cam across this question at stackoverflow:
http://stackoverflow.com/questions/8621247/fastest-way-to-make-vim-use-new-plugin-in-vim-bundles/8621357#8621357
As you can see I suggested to do something like this : map \u call pathogen#infect() to rescan the bundles directory.
Maybe you could provides a default mapping for this and mention somehting in the documentation ? Unless
this happens to be a bad idea for some reason ?
The text was updated successfully, but these errors were encountered: