null-ls.nvim VS lsp-zero.nvim

you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)

here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...

I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.

I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.

Because null-ls.nvim & mason.nvim together do everything I wanted CoC for

There is a good answer. I think you know lua and neovim config enough to pick things that you need. If you need a short answer, null-ls is the way.

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.