vim-pathogen VS vundle

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.

I'm no networking expert, but I think something is wrong with the URL being accessed to download the file. To simplify, just go inside the ~/.vim/autoload folder, create a file named pathogen.vim, open the file, paste the contents of this file and save.

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 ?

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.

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.

Pathogen

git clone https://github.com/tpope/vim-pathogen ~/.vim/bundle

With vim 7.4, there was some tuning to do to manage the runtime path, that's why there are a bunch of plugin managers out there, like the minimalistic, solid vim-pathogen by Tim Pope (again!), vundle, then asynchronous and fast dein, and my favorite Vim-Plug.

I think that's it... it's a very easy and light-weight setup using pathogen in my opinion. Vim now has its own package management built-in, but I still find pathogen easier. Also, you can skip the $HOME env var if you want... I just like giving Vim and other $HOME respecting programs their own place because c:\Users\ is usually filled with other junk.

I'm confused. What install guide are you talking about to be specific (as in, please actually send a link)? The official repository is at https://github.com/VundleVim/Vundle.vim and it doesn't mention Python at all. From what I understand Vundle is not written in Python and should not have a dependency to it. If in doubt, consult official documentation rather than third-party tutorials and guides which could be wrong and/or including extra steps that are not necessary.

Vundle https://github.com/VundleVim/Vundle.vim

For example, a link to Git for Windows on Vundle's wiki was replaced with a link to malware:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_compare/3aeb22ac39229af4312f2be1052ead184dd5b54d...aa3d293dd18ae1cb4f049c43b73b951651515863

In fact, all five recent edits, made by three different accounts, were malicious:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_history

I recommend restricting editing in your GitHub wikis to collaborators only.

## Vundle Install Script function install-vundle() { git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim; sudo gem install vundle-cli; if ! grep -Fxq 'set rtp+=~/.vim/bundle/Vundle.vim' ~/.vimrc then echo "\nset nocompatible\nfiletype off\nset rtp+=~/.vim/bundle/Vundle.vim\ncall vundle#begin()\n\nPlugin 'VundleVim/Vundle.vim'\n\ncall vundle#end()\nfiletype plugin indent on" >> ~/.vimrc; fi }

A typo. I meant vundle. VimBundle