Jedi-vim VS vimspector

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

There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.

I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).

The actual title is "Vimspector - A multi-language debugging plugin for Vim".

It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...

vimspector

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

You could try vimspector. It's main target is vim and not neovim.

https://github.com/puremourning/vimspector/

I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).

[0] https://github.com/ycm-core/YouCompleteMe

[1] https://github.com/puremourning/vimspector

[2] https://github.com/dense-analysis/ale

For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.