As stated in the nvim-lspconfig documentation, elixirls doesn't have set a default cmd field, since nvim-lspconfig doesn't make assumptions about the path.
If somebody installs elixirls through mason.nvim though, the path is definitely $XDG_DATA_HOME/nvim/mason/bin/elixir-ls.
This option could be added to the plugin.
Why do you think this is an issue with mason-lspconfig.nvim?
elixirls installed via mason.nvim has a predefined path that can be already set to have out-of-the-box compatibility with nvim-lspconfig.
Problem description
As stated in the
nvim-lspconfig
documentation,elixirls
doesn't have set a defaultcmd
field, sincenvim-lspconfig
doesn't make assumptions about the path.If somebody installs
elixirls
throughmason.nvim
though, the path is definitely$XDG_DATA_HOME/nvim/mason/bin/elixir-ls
.This option could be added to the plugin.
Why do you think this is an issue with mason-lspconfig.nvim?
elixirls
installed viamason.nvim
has a predefined path that can be already set to have out-of-the-box compatibility withnvim-lspconfig
.Neovim version (>= 0.7)
NVIM v0.7.2 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3
Operating system/version
Linux sicro 5.19.8-gentoo #1 SMP Fri Sep 9 00:17:13 -03 2022 x86_64 AMD Ryzen 7 PRO 4750U with Radeon Graphics AuthenticAMD GNU/Linux
I've manually reviewed the Nvim LPS client log (
:LspLog
) to find potential errorsI've recently downloaded the latest plugin version of mason.nvim, mason-lspconfig.nvim, and nvim-lspconfig
Affected language servers
elixirls
Steps to reproduce
:MasonInstall elixirls
Actual behavior
elixirls
doesn't startExpected behavior
elixirls
startingLspInfo
LspLog
No response
Healthcheck
Screenshots or recordings
The fix to this is adding the path to
elixirls
tocmd