docs: fix for Neovim LSP/Mason

[lcheylus]

• add URL for mason registry
• add URL for mason-lspconfig.nvim plugin (':LspInstall' command)
• add URL for mason.nvim plugin (':MasonInstall v_analyzer' command)

[ttytm]

Thanks for pointing that out. Last time checked, it was installable with lspconfig. If it isn't anymore, a fix should be submitted upstream imho. The LspInstall command is more commonly used for language servers and MasonInstall works then inherently

[lcheylus]

There is no LspInstall command in lspconfig Neovim plugin, see docs => https://github.com/neovim/nvim-lspconfig/blob/master/doc/lspconfig.txt "nvim-lspconfig does not install language servers for you"
The lspconfig Neovim plugin is only used for LSP servers configuration, Mason is used for installation. Personally, I always install manually my LSP servers (C, Go, Rust, Lua, Python) manually, not via Mason.

I don't know how you were able to run it ?!?!

[spytheman]

Can we keep both?

note: personally I do not use neovim, so it may not make sense at all, in which case, tell me to shut up.

[lcheylus]

Can we keep both?

No, reference to :LspInstall must be removed in README: this command does not exist in Neovim lspconfig plugin.

[ttytm]

Yep it's true what you are saying for default lspconfig. I'm referring to mason-lspconfig

[ttytm]

https://github.com/williamboman/mason.nvim?tab=readme-ov-file#how-to-use-installed-packages also lists mason-lspconfig to use it for lsp installation, so i'd argue it's more ideomatic in the eco system.

[ttytm]

Can we keep both?

note: personally I do not use neovim, so it may not make sense at all, in which case, tell me to shut up.

Weighing up the options and beeing over pedantic:
Keeping it both is no harm and would prevent such misconceptions. Tho if users have missed to install mason-lspconfig and only use mason.nvim they are missing out on some features that's are intended to work together. So forcing them towards there luck might eventually be better for the users. If someone knows about it and is deliberately not using it MasonInstall still works for those who know what they are doing

Edit: please don't mind the spelling issues, I'm having accessibility issues on my phone here 😅

[lcheylus]

Weighing up the options and beeing over pedantic:
Keeping it both is no harm and would prevent such misconceptions. Tho if users have missed to install mason-lspconfig and only use mason.nvim they are missing out on some features that's are intended to work together. So forcing them towards there luck might eventually be better for the users. If someone knows about it and is deliberately not using it MasonInstall still works for those who know what they are doing

OK, I finally understood the error in README for Neovim configuration: :LspInstall is a command to install v-analyzer server with mason-lspconfig.nvim plugin, not lspconfig plugin (2 differents Neovim plugins: one for LSP configuration, the other for installation).

I will modify my PR to keep the both methods for installation:

• :LspInstall with mason-lspconfig.nvim plugin
• :MasonInstall with mason.nvim plugin

[lcheylus]

Fix my PR:

• add URL for mason registry
• add URL for mason-lspconfig.nvim plugin (':LspInstall' command)
• add URL for mason.nvim plugin (':MasonInstall v_analyzer' command)

[ttytm]

I just see we already have both commands (I only addressed the commonts on my phone yesterday without checking the diff). In my memory it was just LspInstall without mentioning nvim-lspconfig. My comment regarding weighing up not to add MasonInstall makes less sense than.

Clarifying the current commands is fine 👍

[spytheman]

Is it good to merge as it is now?

[lcheylus]

Is it good to merge as it is now?

Yes :)