3 ms·
Make sure you have rust-analyzer installed, and check `hx --health` to see that Helix finds it. Not sure if this is still necessary, but I needed this workarou
by exDM69 4y ago
Make sure you have rust-analyzer installed, and check `hx --health` to see that Helix finds it.
Not sure if this is still necessary, but I needed this workaround in ~/.config/helix/languages.toml:
language-server = { command = "rustup", args = ["run", "nightly", "rust-analyzer"]}
This should not be necessary when rust-analyzer is stabilized (may be already), but last time I tried it still needed nightly.
- aussiesnack 4y agoThanks. Hadn't realised I needed to have the lsp server binary on the path. I think nvim-lspconfig takes care of that for me in nvim. From a brief experiment basic lsp usage seems to work in helix without any config changes, so perhaps that's changed since you set it up.
- davidatbu 4y agoI'm sure that nvim-lspconfig doesn't take care of installing binaries for LSP servers like this. You either set the path to the binary in your config, or you are using another neovom plugin to make sure LSP server binaries are installed
- aussiesnack 4y agoNo you're right it was mason, which installs lsp servers to a location it manages. I had set it up once and then forgotten. The complexity of all the interacting packages needed with neovim does add to helix's appeal.