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/e36227b2ea0e7807f9132abdc71e11ecaf7c36ec/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
This commit is contained in:
Artem Zhurikhin authored and GitHub committed 2025-06-18 19:08:50 +00:00
1 parent 97cb3a31a5
commit bea1a0f99c
1 file changed
+2 -2
+2 -2
View File
@@ -78,7 +78,7 @@ If you want to disable Zed looking for a `rust-analyzer` binary, you can set `ig
}
```
If you want to use a binary in a custom location, you can specify a `path` and optional `args`:
If you want to use a binary in a custom location, you can specify a `path` and optional `arguments`:
```json
{
@@ -86,7 +86,7 @@ If you want to use a binary in a custom location, you can specify a `path` and o
"rust-analyzer": {
"binary": {
"path": "/Users/example/bin/rust-analyzer",
"args": []
"arguments": []
}
}
}