Unable to configure Crush to work correctly with Rust.

[ksze]

I'm using Crush from PowerShell 7.5 on Windows 11. I have this in my global crush.json config:

{
  "lsp": {
    "rust": {
      "command": "rust-analyzer",
      "enabled": true
    }
  }
}

I have the latest Rust toolchain as of this writing:

rustc --version                                                                                                                                                                                                                                                         rustc 1.93.1 (01f6ddf75 2026-02-11)

rust-analyzer --version
rust-analyzer 1.93.1 (01f6ddf7 2026-02-11)

I then created a bare-bones Rush project using cargo init. When I ask Crush to develop an app from that project, I see this weirdness.

What does it even mean?

1. Isn't rls deprecated in favour of rust-analyzer? Why is Crush trying to start rls?
2. Why is rls stuck in this "starting..." state?
3. Why does rust also give me E15 H1? The project is bare-bones with a src/main.rs file that looks like this:

fn main() {
    println!("Hello, world!");
}

[andreynering]

Hi @ksze, thanks for reporting this.

I just noticed that rls is indeed deprecated. I opened a patch to remove it from the list so it doesn't load automatically anymore:

• fix(powernap): remove rls which was deprecated in favor of rust-analyzer x#784

I believe that it will be included in the next release, maybe still today.

With regard to the duplicated rust and rust_analyzer LSPs in your screenshot, that will be fixed if you just remove the "rust" key from your config. Crush load common LSPs automatically, and rust_analyzer is one of them, so you don't need to explicitly enable it.

[andreynering]

Closing as fixed in:

• fix(powernap): remove rls which was deprecated in favor of rust-analyzer x#784
• chore: update x/powernap #2295