4 ms·

I would love to know why they have chosen Pathogen instead of Vundle to manage plugins. As hard as I try, I can't see any reasons why Pathogen is greater than V

I would love to know why they have chosen Pathogen instead of Vundle to manage plugins. As hard as I try, I can't see any reasons why Pathogen is greater than Vundle. Can someone enlighten me?

SkyMarshal 13y ago
Chalk it up to different preferences. I prefer Vundle too, never could get Pathogen to work, but Vundle just does for me. But others were using Pathogen before Vundle appeared and have no reason to switch.
- robinhood 13y ago
  Everyone used Pathogen before Vundle, as Pathogen is older. However after an extensive use of Vundle, it's the fastest way to deploy your environment from scratch - or to add, modify or delete a plugin. I really don't troll here - but honestly, managing plugins with Vundle is such a joy that I don't see why a company like Square releases a Vim project using Pathogen. And I'd looveeeee to know the reasons - is it indeed because of personal preferences or is there something I'm missing?
- VeejayRampay 13y ago
  What do you mean you could "never get it to work"? https://github.com/tpope/vim-pathogen#installation https://github.com/tpope/vim-pathogen#installation It's literally copy and paste. I understand preferences and taste, but you make it sound like you need a degree in particle physics to make the thing work...
  - SkyMarshal 13y ago
    I know, and back when I tried it, which was probably years ago, the problem was .vimrc line execute pathogen#infect() always errored out. Couldn't figure out why at the time, then found Vundle, it worked perfectly, been using it since.
- lsiebert 13y ago
  I prefer NeoBundle over Vundle. Lazy loading plugins is great.
johncoltrane 13y ago
Pathogen and Vundle have different purposes: one could be called a "runtimepath manager, it injects the plugins found in ~/.vim/bundle into Vim's runtimepath like if they were installed the standard way, while the other is really a "plugin manager", allowing you to update, install, delete, deactivate plugins. Because they have different purposes, they must be compared according to your needs. I don't need a "plugin manager" but I like my plugins to be organized cleanly so I use Pathogen. If you need something to help you "manage" your plugins, Vundle is a sensible choice but you should compare with VAM or neobundle. In short, comparing Pathogen and Vundle makes no sense: compare what's comparable.

I would love to know why they have chosen Pathogen instead of Vundle to manage plugins. As hard as I try, I can't see any reasons why Pathogen is greater than Vundle. Can someone enlighten me?

SkyMarshal 13y ago

Chalk it up to different preferences. I prefer Vundle too, never could get Pathogen to work, but Vundle just does for me. But others were using Pathogen before Vundle appeared and have no reason to switch.

robinhood 13y ago
Everyone used Pathogen before Vundle, as Pathogen is older. However after an extensive use of Vundle, it's the fastest way to deploy your environment from scratch - or to add, modify or delete a plugin. I really don't troll here - but honestly, managing plugins with Vundle is such a joy that I don't see why a company like Square releases a Vim project using Pathogen. And I'd looveeeee to know the reasons - is it indeed because of personal preferences or is there something I'm missing?
VeejayRampay 13y ago
What do you mean you could "never get it to work"? https://github.com/tpope/vim-pathogen#installation https://github.com/tpope/vim-pathogen#installation It's literally copy and paste. I understand preferences and taste, but you make it sound like you need a degree in particle physics to make the thing work...
- SkyMarshal 13y ago
  I know, and back when I tried it, which was probably years ago, the problem was .vimrc line execute pathogen#infect() always errored out. Couldn't figure out why at the time, then found Vundle, it worked perfectly, been using it since.
lsiebert 13y ago
I prefer NeoBundle over Vundle. Lazy loading plugins is great.

johncoltrane 13y ago

Pathogen and Vundle have different purposes: one could be called a "runtimepath manager, it injects the plugins found in ~/.vim/bundle into Vim's runtimepath like if they were installed the standard way, while the other is really a "plugin manager", allowing you to update, install, delete, deactivate plugins. Because they have different purposes, they must be compared according to your needs. I don't need a "plugin manager" but I like my plugins to be organized cleanly so I use Pathogen. If you need something to help you "manage" your plugins, Vundle is a sensible choice but you should compare with VAM or neobundle. In short, comparing Pathogen and Vundle makes no sense: compare what's comparable.