Stream: t-compiler/rust-analyzer

Topic: nvim-lsp cargoFeatures


Wojciech Polak (Nov 12 2020 at 11:40, on Zulip):

Hey, is anyone here using nvim-lsp (native built-in LSP client for neovim 0.5.0 branch) with RA? If so, how can I enable features like rust-analyzer.cargoFeatures.loadOutDirsFromCheck? Is this json format VSCode thing?

matklad (Nov 12 2020 at 11:41, on Zulip):

https://github.com/neovim/nvim-lspconfig/pull/199 should help

matklad (Nov 12 2020 at 11:49, on Zulip):

And inside that dictionary, I think you need nested keys: {cargoFeatures: { loadDirsFromCheck: true}}, or whatever is the lua synta for this.

Wojciech Polak (Nov 12 2020 at 12:22, on Zulip):

Ah thank you! Your MR directed me into package.json file with all settings defined there which I couldn't find. Apparently its no longer cargoFeatures but cargo and thats why it didnt work :)

matklad (Nov 12 2020 at 12:27, on Zulip):

Heh, that explains this

matklad (Nov 12 2020 at 12:27, on Zulip):

alos, urgh, the settings situation is bad -- only VS Code has any semblance of sane configuration, because this is done outside of LSP

matklad (Nov 12 2020 at 12:28, on Zulip):

I need to allocate some time for editor-independent documentation for settings...

Or maybe I should go ahead and suggest and LSP extension for setting scheme....

csmoe (Nov 12 2020 at 17:14, on Zulip):

https://github.com/neovim/nvim-lspconfig/issues/310 btw, the root pattern should be overwritten with .git, or your cpu/mem will be exhausted when working with huge workspace like rustc. @matklad is this a rust-analyzer issue with workspace?

Last update: Jul 27 2021 at 22:00UTC