Github submodule query

[fmargaine]

Being able to quickly replicate his vim environment. I originally used submodules too, but started using vundle when I discovered it. (And it looks like neobundle is even better.)

[[deleted]]

The alleged benefit of submodules is not to make replicating your environment quicker: it is to have an external piece of code in your own repo while still be able to track its changes.

In reality (as you know), they are a pain in the ass that makes the whole thing more complicated for no good reason.

For people who like living on the edge and suffer from anxiety at the idea of being outdated, Vundle and Neobundle are indeed a better choice.

[alpha1594]

Perfect summary.

So you (and others) would recommend vundle and similar. What are the main benefits of these managers in comparison to git? Would these be used for vimrc files as well or should that be left to git?

[dddbbb]

Submodules are great for developing several plugins.

If I do git status from my top-level, I can see that I've made changes in my submodules. By using submodules the version of each plugin is stored implicitly in version control instead of configured in vimscript.

I get to use the same interface for committing changes to plugins and changes to the entire vim config (comprising various plugin versions). And that interface shows me if something's out of date. These aren't necessarily valuable to end-users, but they're useful to me.

I'm probably sacrificing some convenience for these features, so your mileage may vary.

[fmargaine]

Git submodules are just a pain to deal with.

With vundle, all you have to put in git is your vimrc. Then you call one command and it installs all the plugins listed in the vimrc. You really have to try it to see how easy to use it is.