I would like to manage plugins in the lowest-touch way possible, and ideally one that’s easy to migrate to other machines.

I like the idea of the internal plugin manager, but that generally means that I need to manually all the git repos on all machines. It also makes tracking plugins that I’m testing a bit annoying.

The alternative seems to be vundle or vim-plug, which do the git management, but don’t use the internal plugin system.

Are there other options? What’s the easiest these days?

    • naught101@lemmy.worldOP
      2·
      2 days ago

      I already use pathogen, but it doesn’t do the git management that I want. I guess I could use hit in my .vim directory with submodules, but it seems like overkill, and managing updates is still annoying.

      • AnIndefiniteArticle@sh.itjust.works
        2·
        2 days ago

        How often do your vim plugins have updates? What are the value of these updates?

        I use a pretty vanilla/minimalist vim setup and my simple plugins haven’t changed really at all in the past decade.

        • naught101@lemmy.worldOP
          2·
          2 days ago

          The point isn’t so much the updates as ensuring all the plugins are installed the same way across 3+ systems (2 home computers, one work one, sometimes some servers)

            • naught101@lemmy.worldOP
              1·
              2 days ago

              Yeah, that’s about where I’m at. It gets annoying though, with things like YouCompleteMe, which need to be compiled/installed to work properly, and the compilation is different on each architecture. I guess an rsync script with exclusions could work, but it just feels hacky, and like there should be a better way.