Software Alternatives & Reviews

NeoBundle VS pathogen.vim

Compare NeoBundle VS pathogen.vim and see what are their differences

NeoBundle logo NeoBundle

Next generation Vim package manager. Contribute to Shougo/neobundle.vim development by creating an account on GitHub.

pathogen.vim logo pathogen.vim

pathogen.vim: manage your runtimepath. Contribute to tpope/vim-pathogen development by creating an account on GitHub.
  • NeoBundle Landing page
    Landing page //
    2023-09-30
  • pathogen.vim Landing page
    Landing page //
    2023-10-04

Category Popularity

0-100% (relative to NeoBundle and pathogen.vim)
Text Editors
29 29%
71% 71
Software Development
45 45%
55% 55
Programming Tools
100 100%
0% 0
IDE
0 0%
100% 100

User comments

Share your experience with using NeoBundle and pathogen.vim. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, pathogen.vim seems to be more popular. It has been mentiond 6 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

NeoBundle mentions (0)

We have not tracked any mentions of NeoBundle yet. Tracking of NeoBundle recommendations started around Mar 2021.

pathogen.vim mentions (6)

  • Any Suggestions Apart from vscode for Terraform ?
    The person who mentored me the most when I was getting started with Terraform used VIM with pathogen but honestly this isn't a great idea unless you're really invested in a VIM workflow. Source: 10 months ago
  • Vim or Emacs?
    I am a bit confused. What has this anything to do with your original question? vim-pathogen is for Vim editor itself, not for PyCharm. I don't know much about MacOS, so not sure how to help. Did you try the installation steps at https://github.com/tpope/vim-pathogen ? Source: over 1 year ago
  • Usage of 'after/ftplugin' directory for filetype-specific configuration
    Back in the old(ish) days of Vim, usage of tpope/vim-pathogen to manipulate runtimepath was a popular way to install plugins. As it got update 9 days ago, it might be still used by some. Source: over 1 year ago
  • Vim: NERDTree
    To install any plugin using Pathogen plugin manager, you need to configure PAthogen in your vimrc if you have not done it already. You can find the installation docs on Pathogen.vim. After Pathogen has been configured in your vimrc, you can clone the git repository of that plugin into your local machine and then activate it using Pathogen. - Source: dev.to / over 2 years ago
  • Recommendations for "Standard, Modern Vim Config"?
    Bundles, Plugins, and Packages. Oh my! - Vim plugin management have gone through many "best practices". vim-pathogen, Vundle, vim-plug, and Vim 8's :packadd. At any given time I am certain the community would say one of these is "modern" or at the least some sort of standard. Source: almost 3 years ago
View more

What are some alternatives?

When comparing NeoBundle and pathogen.vim, you can also consider the following products

Vim-Plug - :hibiscus: Minimalist Vim Plugin Manager. Contribute to junegunn/vim-plug development by creating an account on GitHub.

SonarLint - Clean Code begins in your IDE with SonarLint - Our free IDE extension that provides on-the-fly analysis and coding guidance.

ale - Asynchronous Lint Engine

Vundle - Vundle, the plug-in manager for Vim. Contribute to VundleVim/Vundle.vim development by creating an account on GitHub.

Vim Awesome - Awesome Vim plugins from across the universe

TabNine - TabNine is the all-language autocompleter. We use deep learning to help you write code faster.