vscode-java-debug VS nvim-dap

Now I wish to install nvim-dap to debug java applications. I already have nvim-jdtls installed, which nvim-dap needs. But for full debuggin capabilities I need to have java-debug and vscode-java-debug insalled as stadet in nvim-jdtls#debugger-via-nvim-dap.

You can set the java.debug.settings.console setting to internalConsole, which will give you less verbose output in the debug console. Note that the debug console doesn't support user input, so if you need that you'll have to use the more verbose integratedTerminal option (the default). I've submitted a feature request to the extension for a less verbose pseudoterminal that supports user input, see microsoft/vscode-java-debug#906 if you want to voice your opinion (currently it seems like the devs are not prioritizing it).

Anyone knows why? I searched for a while and I found an issue on GitHub but it seems like it's not the same case.

I've found the issue, and reported it to the developers of the Java debug extension (see microsoft/vscode-java-debug#970). Let's hope it gets fixed quickly, but in the meantime there is a workaround for those using JDK16.

You could set the java.debug.settings.console setting to internalConsole, to use the Debug Console instead of a terminal (which only shows the program output). The problem with that approach is that the Debug Console doesn't support user input. So if you want to have less verbose program output and and support for user input, I suggest you go upvote or comment microsoft/vscode-java-debug#906 to show that there's any demand for the feature.

You can choose to display the program output in the debug console by setting java.debug.settings.console to internalConsole, which I believe will achieve what you're after. The only downside is that it doesn't support user input, you have to use the terminal for that. If you care about that feature, and want a proper solution, you can upvote or comment microsoft/vscode-java-debug#906.

If you still want this feature, you can put a feature request in vscode-java for production group to determine if it's necessary to develop this function.

WSL is also unsupported for a different reason: there's no (easy) way to launch .bat scripts in WSL, but the Java Debug extension relies on such a script to launch the debug session on Windows. See microsoft/vscode-java-debug#708 for that issue.

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.

https://github.com/mfussenegger/nvim-dap/issues/1062 https://github.com/mfussenegger/nvim-dap/issues/737

Also, you can set up debugger integration with https://github.com/mfussenegger/nvim-dap .

You could use nvim-dap with nvim-dap-python.

I'd suggest starting with a Neovim distro that makes things work for you and as you get familiar you can transition to a more custom configuration as you see fit. If you want to do it by yourself then the most popular plugin for debugging in Neovim is nvim-dap and there is also an extension for Python to give you a more ready to go config instead of doing it yourself. You should read the docs of those 2 to see how you should customize accordingly your configuration.

(neovim only) nvim-dap

https://github.com/mfussenegger/nvim-dap + https://github.com/theHamsta/nvim-dap-virtual-text should be able to do it, I think?

If you want to debug types in TypeScript, you could use marilari88/twoslash-queries.nvim. If you would like to debug TypeScript/JavaScript code, then you need mfussenegger/nvim-dap, you could read this article: Debugging using DAP to understand how to set up it.