# Be more lenient when dealing with rust-analyzer's flycheck commands \(\#36782\) · gitcafe/zed

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

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

Visibility: public

Requested revision: d24cad30f3805f03a4030703701ef77639a028bc

Requested commit: d24cad30f3805f03a4030703701ef77639a028bc

Commit: d24cad30f3805f03a4030703701ef77639a028bc

Tree: f79040f721e12d19d0b62253d8328db27d5cab3f

Author: Kirill Bulatov

Committer: GitHub

## Message

```
Be more lenient when dealing with rust-analyzer's flycheck commands (#36782)

Flycheck commands are global and makes sense to fall back to looking up
project's rust-analyzer even if the commands are run on a non-rust
buffer. If multiple rust-analyzers are found in the project, avoid
ambiguous commands and bail (as before).

Closes #ISSUE

Release Notes:

- Made it possible to run rust-analyzer's flycheck actions from anywhere
in the project
```

## Parents

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

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