vimspector VS vim-plug

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.

vim-plug

Did you really install VimTeX? Did you run :PlugInstall? Ensure you installed and set up vim-plug correctly (https://github.com/junegunn/vim-plug). If VimTeX is installed, it should be installed to '~/.vim/plugged', thus you can open a terminal, then cd ~/.vim/plugged/vimtex and you should find the files there.

If you're determined to use vim for some reason, I'd suggest checking out vim-plug: https://github.com/junegunn/vim-plug. Quite useful for installing and maintaining all of the plugins that you're going to need to get vim to provide even a subset of the features offered by modern editors.

I encourage you to add plugins to your vim (tip: use vim-plug). Use vimawesome.com for inspiration.

Personally, I like https://github.com/junegunn/vim-plug

But the plugin manager https://github.com/junegunn/vim-plug can also install from offline sources, without accessing Github:

To get started, simply install the plugin using your favorite plugin manager, such as vim-plug or packer.nvim. You can find detailed installation instructions in the README.

Not sure if Vundle did anything particularly fancy, but I'm using vim-plug [0] and have no complaints. It stays out of my way to the point that I had to look at my .vimrc just now to make sure that's what I was using.

[0] https://github.com/junegunn/vim-plug

I chose to move on to vim-plug and can report it was a simple switch from Vundle.