docs: Fix lsp.rust-analyzer.binary
config (#32967)
Document the `lsp.rust-analyzer.binary.arguments` setting (currently
incorrectly referred to as `args`)
Verify:
99215f7660/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:
parent
fdd307cf7a
commit
ccb4644365
1 changed files with 2 additions and 2 deletions
|
@ -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
|
```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": {
|
"rust-analyzer": {
|
||||||
"binary": {
|
"binary": {
|
||||||
"path": "/Users/example/bin/rust-analyzer",
|
"path": "/Users/example/bin/rust-analyzer",
|
||||||
"args": []
|
"arguments": []
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue