Skip to main content
edited tags
Link
Martin Tournoij
  • 64.3k
  • 27
  • 205
  • 280
removed potentially problematic "what's the best way"
Source Link
Tom
  • 1.3k
  • 11
  • 12

I know many people store their .vimrc on GitHub to make it easier to get right to work on new machines, and that makes complete sense to me. I'm confused about doing that withIncluding plugins, thoughhowever, as each plugin is a repo on its ownproblematic, and my understanding is that nestingbecause the plugins I use are already git repositories is a Bad Move. What's the best way to store everythingHow does one create a repo that makes your Vimwill track both their yours on GitHub—or is GitHub not the answer.vimrc and any plugins that might be installed?

I know many people store their .vimrc on GitHub to make it easier to work on new machines, and that makes complete sense to me. I'm confused about doing that with plugins, though, as each plugin is a repo on its own, and my understanding is that nesting repositories is a Bad Move. What's the best way to store everything that makes your Vim yours on GitHub—or is GitHub not the answer?

I know many people store their .vimrc on GitHub to make it easier to get right to work on new machines, and that makes complete sense to me. Including plugins, however, is problematic, because the plugins I use are already git repositories. How does one create a repo that will track both their .vimrc and any plugins that might be installed?

Source Link
Tom
  • 1.3k
  • 11
  • 12

GitHub for .vimrc and plugins

I know many people store their .vimrc on GitHub to make it easier to work on new machines, and that makes complete sense to me. I'm confused about doing that with plugins, though, as each plugin is a repo on its own, and my understanding is that nesting repositories is a Bad Move. What's the best way to store everything that makes your Vim yours on GitHub—or is GitHub not the answer?