Jedi-vim VS vim-pathogen

jedi-vim does autocomplete, docstring/signature/stub lookup, usage finding, bulk renaming...

The readme for jedi-vim says it works with Python 3:

To be able to use ctags you have to run ctags in the source directory to generate the index files. But a better way is to just modify the keywordprg when in a Python buffer or even better use a plugin like pydoc.vim or jedi-vim

I added https://github.com/davidhalter/jedi-vim to my plugins in ~/.config/nvim/init.vim and ran PlugInstall and it worked, but whenever I try to open a python file and the autocomplete part should come up I get

But LSP is a critical part of my Python setup, where I use David Halter's jedi-vim for completion, renaming, go-to-definition, finding usages of variables, etc., so I'm definitely not opposed to LSP on principle. I guess I just found Latex wasn't a complicated enough language for me to benefit from the full suite of features an LSP provides.

Install linux (WSL) with this tutorial (assuming you are on windows) and go through this tutorial to get used to it. To write python scripts, use vim and install this plugin.

I think you can get that behavior with https://github.com/davidhalter/jedi-vim but I haven't tried it.

Firstly I will like to install Jedi for code completion in Python. The plugin can be simple and straightforward to install using any of the above plugin managers. Jedi-Vim provides some neat and clean** syntax analytics and autocompletion for Python in Vim**. You'll find the docs and installation process here JEDI-VIM

I've never used it, not really a python gal, but from what I read, jedi sounds like a good one (https://github.com/davidhalter/jedi-vim).

See https://github.com/davidhalter/jedi-vim

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.