diagnosticls-configs-nvim VS formatter.nvim

More info on installation and setup can be found in the plugin repo: https://github.com/creativenull/diagnosticls-configs-nvim

I tried using this config: https://github.com/creativenull/diagnosticls-configs-nvim/blob/main/lua/diagnosticls-configs/linters/luacheck.lua

I was taking a look at https://github.com/creativenull/diagnosticls-nvim to set up linting and formatting, it has some easy to set config but it still hits me: is there some kind of "ready to go" plugin or setting for neovim lsp?

I use diagnosticls and nvim-lsp-ts-utils.

Can anyone explain why someone would use null-ls if you're using the modern lsp setup (say, from kickstart.nvim). I see comments mentioning formatting. I see formatters mentioned several times. Why not just use https://github.com/mhartington/formatter.nvim?

I use null-ls (https://github.com/jose-elias-alvarez/null-ls.nvim), I haven't tried it for python, but haven't had trouble with lua, js, ts or rust. You can also look into formatter.nvim (https://github.com/mhartington/formatter.nvim).

I use formatter.nvim for formatting

For formatting, formatter.nvim is a good choice and has similar setup to nvim-lint.

I finally installed this formatter plugin and configured it to execute de clang-format command like this

mhartington/formatter.nvim is used for automatic code formatting. Its configuration also shows how to use nvim_create_augroup and nvim_create_autocmd from Lua.

This might have something to do with extmarks being clobbered when the new text is written. For example, here is a GitHub issue describing the problem: https://github.com/mhartington/formatter.nvim/issues/22 This is for formatter.nvim, but this would likely apply to any process that rewrites the whole buffer.

i have always had trouble with lsp formatting and null-ls (may just be me, i'm not super clued in) so i use formatter.nvim https://github.com/mhartington/formatter.nvim/

Take a look at formatter.nvim

I've had really good experience with formatter-nvim.