4 ms·

While I appreciate your comment, we can already guess that you believe the packages you have chosen to be “the best” at their job. Without further narration (an

While I appreciate your comment, we can already guess that you believe the packages you have chosen to be “the best” at their job. Without further narration (and I’ve only singled you out due to being the topmost comment), comment sections like this have a tendency to become a dumping ground for vimrc snippets. Could you expand on why? Personally I’d be particularly interested on your thoughts about vim-plug, as I use pathogen currently and I seems to do everything I need.

farresito 8y ago
- You can update all the plugins with PlugUpdate; furthermore, they are updated in parallel. - You can lazy load plugins - You can execute commands after a plugin update (e.g. building the new binary for youcompleteme) Those are the major points I think.
- jessaustin 8y ago
  Lots of people like plugin managers. I prefer to use "git clone" and "stow". Much less magical, and I feel I have a better understanding of what's going on with my configuration.
  - pfranz 8y ago
    I have a plugin manager that can help you with that! Seriously, isn't part of the problem that vim by default looks for all plugins in one directory? Tim Pope's Pathogen does the minimum here and lets each plugin have its own directory (which translates to git repo). You're responsible for going to each directory and updating them.
    - AdamGibbins 8y ago
      Git submodules handle that for me, also allows me to easily rollback.
    - deleted 8y ago
      [deleted]
    - jessaustin 8y ago
      I'm doing that too. I clone into "~/.config/nvim/stow/", then stow figures out how to put all that stuff into the proper places. Occasionally there is a conflict, but that is usually for files that I don't want anyway, like "build" or "LICENSE".
- sodapopcan 8y ago
  Plugin managers are also nice because you can maintain a list of plugins right in your vimrc. Not the biggest win in the world if you are fine managing your plugins via a shell script, but it's a win to many. My favourite thing about vim-plug is its `:PlugDiff` command which, after running `:PlugUpdate` will load all the new commits in an explorable vim buffer, so you can see exactly what changed and even easily see code changes.

farresito 8y ago

- You can update all the plugins with PlugUpdate; furthermore, they are updated in parallel. - You can lazy load plugins - You can execute commands after a plugin update (e.g. building the new binary for youcompleteme) Those are the major points I think.

jessaustin 8y ago
Lots of people like plugin managers. I prefer to use "git clone" and "stow". Much less magical, and I feel I have a better understanding of what's going on with my configuration.
- pfranz 8y ago
  I have a plugin manager that can help you with that! Seriously, isn't part of the problem that vim by default looks for all plugins in one directory? Tim Pope's Pathogen does the minimum here and lets each plugin have its own directory (which translates to git repo). You're responsible for going to each directory and updating them.
  - AdamGibbins 8y ago
    Git submodules handle that for me, also allows me to easily rollback.
  - deleted 8y ago
    [deleted]
  - jessaustin 8y ago
    I'm doing that too. I clone into "~/.config/nvim/stow/", then stow figures out how to put all that stuff into the proper places. Occasionally there is a conflict, but that is usually for files that I don't want anyway, like "build" or "LICENSE".
sodapopcan 8y ago
Plugin managers are also nice because you can maintain a list of plugins right in your vimrc. Not the biggest win in the world if you are fine managing your plugins via a shell script, but it's a win to many. My favourite thing about vim-plug is its `:PlugDiff` command which, after running `:PlugUpdate` will load all the new commits in an explorable vim buffer, so you can see exactly what changed and even easily see code changes.