lsp-zero.nvim VS asyncrun.vim

I'm using lsp-zero and i followed this tutorial https://github.com/VonHeikemen/lsp-zero.nvim/blob/v2.x/doc/md/guides/setup-with-nvim-jdtls.md and i have essentially just copy pasted the code from there into ~/.config/nvim/lua/plugin/jdtls.lua

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

For those new to neovim, the documentation in lsp-zero has a tutorial that shows a configuration from scratch. It shows how to get a plugin a manager, a colorscheme, and setup lsp-zero.

Try https://github.com/VonHeikemen/lsp-zero.nvim, a great introduction and it is pretty usable without any further config

For neovim, you can still use the same extensions; however there's also a built-in LSP client. The downside of using the built-in is you'll need to have more extensions installed/configured to get all the features out of the box...BUT projects do exist to help simplify that, like lsp-zero.

lap-zero.nvim - default config for nvim-lspconfig, mason.nvim, nvim-cmp.

In version v2.x the keybindings you set on the "global" on_attach of lsp-zero should work without any extra config. v2.x also has a tutorial on how to work with nvim-jdtls: setup with nvim-jdtls

Creator of lsp-zero suggested a complete solution to use ray-x/lsp_signature in this issue: https://github.com/VonHeikemen/lsp-zero.nvim/issues/69.

I'm familiar with asyncrun.vim, but it outputs as quickfix. I specifically want to filter editor text (as stdin/stdout).

If you want to open a new terminal in the CWD of neovim, you couls either use neovim's built in terminal or, if it needa to be kitty, use the neovim AsyncRun-plugin and start kitty with the necessary command-line options to start in neovims's CWD(I uae this with Alacritty instead of Kitty).

For running the file there are several tools. I have been using asynctasks.vim which is built on top of asyncrun.vim which I usually use to open a tmux pane and run the code/test. I've been looking at switching to overseer.nvim but haven't yet. I use justfiles to define all of my tasks.

I can :Man blah to look up docs or :AsyncRun to build/run with jumpable output in the quickfix. Doing it within vim means I can pull from any register for pasting, yank without a mouse, hide buffers or move them to tabs, etc.

I use asyncrun.vim to see compile output as it happens (line by line instead of the whole dump when compile completes) and asynchronously (so I can keep navigating around).

try asyncrun:

Also AsyncRun and AsyncTasks worth a mention.

Hey folks, I'm using asyncrun to run async commands on vim, but some of them output ansi colorcodes, I've found powerman's AnsiEsc which is able to conceal and highlight them very well, but that only work for the current buffer, so there's no way to automate it from g:asyncrun_exit and I can't set the -post from asynctasks, has anyone found a way to fix this?

As you can see, I use asyncrun.nvim since sometime compiling/running will take quite long. For some complex situations, like c++ project with cmake, I use following code: