coc-java VS vimspector

Java

Check out the coc.java README, it uses jdt.ls under the hood and it supports gradle projects and maven projects (both of them wre Java build tools and dependency managers for big projects).

Just follow the directions on the eclipse-jdt.ls and coc-java on the installation process, I have no clue about that as I don't develop in java

A fork of the VSCode extension, coc-java is used by coc.nvim to provide Java support for Vim/NeoVim.

Looking through the internet I've found through https://github.com/neoclide/coc-java/issues/27#issuecomment-506283639 that `java.jdt.ls.vmargs` needs to be set. But that option is for `coc` and I want to use inbuilt `lsp` client.

If you're not using Neovim, then coc https://github.com/neoclide/coc.nvim is probably the best LSP implementation. https://github.com/neoclide/coc-java installs the eclipse language server for autocomplete, linting etc.

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.