# languages: Use rustup rust-analyzer when toolchain override is present \(\#57696\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/b20cd411ec792dc441705bbbeb4cc3ac88664ca0)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: b20cd411ec792dc441705bbbeb4cc3ac88664ca0

Requested commit: b20cd411ec792dc441705bbbeb4cc3ac88664ca0

Commit: b20cd411ec792dc441705bbbeb4cc3ac88664ca0

Tree: 36a51c27eef8e75d31557c60418c0015c01d0a92

Author: Lukas Wirth

Committer: GitHub

## Message

```
languages: Use rustup rust-analyzer when toolchain override is present (#57696)

rust-analyzer does not really attempt to be backwards compatible, so
when users opt-into the component a toolchain override, we should prefer
that over any other rust-analyzer (especially our own) for better
toolchain compatibility in case people have a more out of date install.
This mirrors the VSCode extension behavior

Release Notes:

- When a worktree contains a Rust toolchain file with a rust analyzer
component specified, Zed will now spawn the given toolchain's
rust-analyzer for toolchain compatability
```

## Parents

- [a8966695ee9fdbf4aac241a7a9514639263183f1](https://git.cafe/gitcafe/zed/commit/a8966695ee9fdbf4aac241a7a9514639263183f1?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/b20cd411ec792dc441705bbbeb4cc3ac88664ca0?format=markdown)