[BUG] rust-analyzer stops providing diagnostics without clear reason about nixvim

[GaetanLepage]

This is weird, and I don't know what could cause this.
However, the thing to try first is to set plugins.lsp.servers.rust-analyzer.installCargo and plugins.lsp.servers.rust-analyzer.installRustc to false.
Like so, the LSP will fall back to using the cargo/rustc from your environment.

[vsiles]

Looks like it works !
In my config I'm using rustaceanvim instead of configuring rust-analyzer all by myself. Doing what you wrote made the error disappear, but I now have two RA running with the message:

nvim-lspconfig.rust_analyzer has been setup.
This will likely lead to conflicts with the rustaceanvim LSP client.
See ':h rustaceanvim.mason'

I tried to change my config in this way:

      rustaceanvim = {
        enable = true;
        settings = {
          server = {
            default_settings = {
              rust-analyzer = {
                installCargo = false;
                installRustc = false;
                cargo = {
                  allFeatures = true;
                };
                check = {
                  command = "clippy";
                };
                inlayHints = {
                  lifetimeElisionHints = {
                    enable = "always";
                  };
                };
              };
            };
            standalone = false;
          };
        };
      };

but it didn't work. I'll continue to see how I can avoid that warning message ;)

[vsiles]

Feels like I have to enable rust-analyzer (https://github.com/nix-community/nixvim/blob/main/plugins/lsp/language-servers/rust-analyzer.nix#L40) for the installCargo/Rustc option to be taken into account.
Do you think there's a way around that without pulling the checks out of the lib.mkIf ?

[vsiles]

@GaetanLepage do you know of a way to configure installCargo and installRustc to false while using rustaceanvim and not rust-analyzer directly ?