neovim-luca VS vscode-java-debug

Hello guys. I installed neovim using my own nix flake: https://github.com/quoteme/neovim-luca

outputs = {self, nixpkgs}: let pkgs = nixpkgs.legacyPackages.x86_64-linux; # ┏━┓╻ ╻ ╻┏━╸╻┏┓╻┏━┓ # ┣━┛┃ ┃ ┃┃╺┓┃┃┗┫┗━┓ # ╹ ┗━╸┗━┛┗━┛╹╹ ╹┗━┛ cmp-nvim-lsp = (pkgs.vimPlugins.cmp-nvim-lsp.overrideAttrs (old: { src = pkgs.fetchFromGitHub { owner = "hrsh7th"; repo = "cmp-nvim-lsp"; rev = "f93a6cf9761b096ff2c28a4f0defe941a6ffffb5"; sha256 = "02x4jp79lll4fm34x7rjkimlx32gfp2jd1kl6zjwszbfg8wziwmx"; }; })); nvim-cmp = (pkgs.vimPlugins.nvim-cmp.overrideAttrs (old: { src = pkgs.fetchFromGitHub { owner = "hrsh7th"; repo = "nvim-cmp"; rev = "af70f40d2eb6db2121536c8df2e114af759df537"; sha256 = "1sv6hsfa1anax7dvp9h83m4z50kpg51fzvvmjb15jjfdih5zmcdb"; }; })); vim-skeleton = pkgs.vimUtils.buildVimPlugin { name = "vim-skeleton"; src = pkgs.fetchFromGitHub { owner = "noahfrederick"; repo = "vim-skeleton"; rev = "v0.5.0"; sha256 = "001fgylvfd1hnzh5cd1kp29yibim69psbz3358xv74b1va9f2dpp"; }; }; vim-sage = pkgs.vimUtils.buildVimPlugin { name = "vim-sage"; src = pkgs.fetchFromGitHub { owner = "petRUShka"; repo = "vim-sage"; rev = "702b29ea80f063f6c9080fefa4132226ea0ad664"; sha256 = "sha256-rXxLP09u2t21P/q3yAeZUglIns0Yc7SGKLQ/RxDrNqs="; }; }; # ┏┳┓┏━┓╻┏┓╻ # ┃┃┃┣━┫┃┃┗┫ # ╹ ╹╹ ╹╹╹ ╹ myneovim = (pkgs.neovim.override { configure = { customRC = pkgs.lib.readFile ./init.vim; packages.myVimPackages = with pkgs; with vimPlugins; { start = [ # Theme onedark-vim # Programming Language Specific stuff # Sage vim-sage # Nix vim-nix # Clojure vim-dispatch vim-dispatch-neovim vim-jack-in conjure vim-repeat vim-surround vim-sexp vim-sexp-mappings-for-regular-people # General help vim-slime vim-signify vim-css-color tabular vim-matchup delimitMate nvim-ts-rainbow fzf-vim vim-commentary vim-multiple-cursors which-key-nvim vim-skeleton (nvim-treesitter.withPlugins (plugins: pkgs.tree-sitter.allGrammars)) nvim-lspconfig # Completion cmp-nvim-lsp nvim-cmp cmp-buffer cmp-vsnip vim-vsnip cmp-path ]; opt = []; }; }; }); in { defaultPackage.x86_64-linux = pkgs.stdenv.mkDerivation rec { version = "0.1"; pname = "neovim-luca"; src = ./.; buildInputs = with pkgs; [ myneovim # ╻ ┏━┓┏┓╻┏━╸╻ ╻┏━┓┏━╸┏━╸ ┏━┓┏━╸┏━┓╻ ╻┏━╸┏━┓ # ┃ ┣━┫┃┗┫┃╺┓┃ ┃┣━┫┃╺┓┣╸ ┗━┓┣╸ ┣┳┛┃┏┛┣╸ ┣┳┛ # ┗━╸╹ ╹╹ ╹┗━┛┗━┛╹ ╹┗━┛┗━╸ ┗━┛┗━╸╹┗╸┗┛ ┗━╸╹┗╸ # LaTex texlab # Haskell haskell-language-server ormolu # JavaScript / Typescript nodePackages.javascript-typescript-langserver # NIX rnix-lsp # Python pyright # Rust rls # Clojure clojure-lsp # C clang-tools # ╺┳╸┏━┓┏━┓╻ ┏━┓ # ┃ ┃ ┃┃ ┃┃ ┗━┓ # ╹ ┗━┛┗━┛┗━╸┗━┛ fzf ripgrep bat toilet xclip ]; installPhase = '' mkdir -p $out/bin # this makes it possible for my neovim to be called using nvim # or vim inside of a terminal ln -sf ${myneovim}/bin/nvim $out/bin/neovim-luca ln -sf ${myneovim}/bin/nvim $out/bin/nvim ln -sf ${myneovim}/bin/nvim $out/bin/vim ''; meta = with pkgs.lib; { author = "Luca Leon Happel"; description = ""; homepage = "https://github.com/Quoteme/neovim-luca"; platforms = platforms.all; mainProgram = "neovim-luca"; }; }; # defaultApp.x86_64-linux = { type = "app"; program = "nvim"; }; }; }

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.