pathogen.vim VS Atom-IDE

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

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

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

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

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

Not a stupid question at all! It is just a code editor. They do have an IDE for compiling ( https://ide.atom.io ) but I haven’t used it so I’m not sure about it’s capabilities. Source: almost 2 years ago

Gotcha! Although it’s no longer maintained, I’ve had no issues with the Atom IDE package. It contains a lot of the same features that you’d expect like code completion, code linting to check for errors before you compile, and the ability to build and run from the Atom editor. Source: over 2 years ago