stow_dotfiles VS mason-null-ls.nvim

(You can find my whole NeoVim configuration here : https://gitlab.com/J.pilleux/stow_dotfiles/-/tree/master/nvim_light/.config/nvim)

I followed the default configuration with Lazy.nvim I found of the github page of mason-null-ls : https://github.com/jay-babu/mason-null-ls.nvim

I will update mason-null-ls: https://github.com/jay-babu/mason-null-ls.nvim#available-null-ls-sources. It is inaccurate since this commit. As long as the convention is followed (aka something-like in mason and something_like in null-ls) exceptions aren't needed. Exceptions live here: https://github.com/jay-babu/mason-null-ls.nvim/blob/main/lua/mason-null-ls/mappings/source.lua

You can use mason-null-ls.nvim also, is a similar bridge to the mason-lspconfig plugin. The plugin translates the server names between mason and null-ls so u just have to add the servers you want to use.

Personally I don’t use linters inside of the editor itself, but I do use formatters. For that I use null-ls which also works for linters, and allows you to configure them (eg. pass arguments to the binary) and hooks them as regular language servers, so you could look into that. The formatters can also be installed through mason but there’s also this plugin which says it’s a bridge to use mason and null-ls (I haven’t tried it, for me things just work with mason and null-ls).

Let me know your thoughts on https://github.com/jayp0521/mason-null-ls.nvim :), just updated the docs. Note: this plugin doesn't do any extra setup outside what is requested.