pathogen.vim VS ti-vim

• Ease of Use
  Pathogen.vim simplifies the management of Vim plugins by allowing users to easily install, update, and remove plugins without altering Vim's core files. It requires minimal configuration.
• Directory Structure
  It promotes a cleaner directory structure where each plugin resides in its own directory under .vim/bundle, making it easier to locate and manage individual plugins.
• Compatibility
  Being widely adopted and time-tested, pathogen.vim is compatible with a wide range of plugins. This ensures that users can confidently use popular Vim plugins alongside it.
• No Impact on Startup Time
  Pathogen.vim is lightweight, which means it doesn't significantly affect Vim's startup time, preserving Vim's reputation for speed and efficiency.

Possible disadvantages

• Limited Features
  Compared to modern plugin managers like vim-plug or Vundle, pathogen.vim offers limited features, lacking built-in update mechanisms for plugins or other advanced functionalities.
• Manual Management of Dependencies
  Pathogen.vim requires users to manually manage plugin dependencies and updates, which can become cumbersome when dealing with a large number of plugins.
• Exclusivity of Git for Installation
  Pathogen.vim relies heavily on Git for plugin installation, which might be a limitation for users who prefer or require alternative installation methods.

• Enhanced UI
  ti-vim provides a more modern and intuitive user interface compared to traditional Vim, making it easier for newcomers to learn and use.
• Customization
  It offers extensive customization options, allowing users to tailor the editor to their specific needs and preferences, enhancing productivity.
• Integration
  The platform integrates well with other tools and plugins, extending its functionality beyond just a text editor.
• Performance
  ti-vim maintains a high level of performance, similar to traditional Vim, ensuring it runs smoothly even with large files.

Possible disadvantages

• Learning Curve
  While the UI is enhanced, there is still a learning curve for users who are new to Vim-based editors, as they need to learn commands and shortcuts.
• Plugin Compatibility
  Not all Vim plugins may be compatible with ti-vim, which could limit its extensibility for some users relying on specific plugins.
• Limited Documentation
  There may be limited documentation available for ti-vim, making it harder for users to find solutions to specific issues or to fully utilize all features.
• Dependency on JavaScript
  Being web-based, ti-vim relies on JavaScript, which might not be preferred by users who avoid heavy client-side processing.

• 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: over 3 years 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... Source: almost 4 years 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: about 4 years ago

View more

• I think I've been poisoned by something called vim

  Ti-vim (closed source, one time purchase). Source: almost 4 years ago