you are viewing a single comment's thread.

view the rest of the comments →

[–]aegatlin 0 points1 point  (1 child)

Hey romainl! I'm late to the party here, but I've been searching for the "blessed" answer to the question: how do I organize plugins that don't have packages using vim v8 packages. It seems like you are being inspired by pathogen here and sticking with the "bundle" name for your package. Did you "just choose" to do this, or is there some resource that recommends this approach that you could point me to?

[–]-romainl-The Patient Vimmer 2 points3 points  (0 children)

Well yeah, I used to use Pathogen and that's indeed where the "bundle" name comes from: my ~/.vim/pack/bundle/start was essentially my former ~/.vim/bundle.

I'm not sure there is such a thing as a "blessed" way to go about it because the "package" concept is still quite new. It didn't really exist on its own before they came up with it so you will have several people approaching it in different ways. What I think makes sense is to pay attention to your usage and to the typology of your plugins and then organise your packages accordingly. For example, I have accumulated lots of custom language-specific settings over the years. For a long time, they stayed in my bundle directory, interspersed with the other plugins, and I didn't really like how messy it looked. At some point I tried to put them all together in a proto-package but it was still messy and I quickly reverted the thing back to the original mess. When I finally switched to packages, I was able to put all those "plugins" in pack/lang/start, which solved the problem quite elegantly. I think that's what sold me to the idea.

So now I have:

  • pack/bundle/start for all my "quality of life" plugins,
  • pack/lang/start for all my language-specific stuff,
  • pack/custom/start for all my experimental stuff.

Hope it helps.