# docs: Fix \`lsp.rust-analyzer.binary\` config \(\#32967\) · gitcafe/zed

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

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

Visibility: public

Requested revision: ccb46443650b5fa3dc4102f149eb1f4c08dc4216

Requested commit: ccb46443650b5fa3dc4102f149eb1f4c08dc4216

Commit: ccb46443650b5fa3dc4102f149eb1f4c08dc4216

Tree: c00fa33ea6a168885e35994f236c6741d1d22c9b

Author: Artem Zhurikhin

Committer: GitHub

## Message

```
docs: Fix `lsp.rust-analyzer.binary` config (#32967)

Document the `lsp.rust-analyzer.binary.arguments` setting (currently
incorrectly referred to as `args`)

Verify:
https://github.com/zed-industries/zed/blob/99215f7660a722461792e49cb920bfda5c801286/crates/extension_api/wit/since_v0.1.0/settings.rs#L24-L29

Question: can such inconsistencies be avoided by automatically
documenting the config using a preprocessor?

Release Notes:

- N/A
```

## Parents

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

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