From ccb46443650b5fa3dc4102f149eb1f4c08dc4216 Mon Sep 17 00:00:00 2001 From: Artem Zhurikhin Date: Wed, 18 Jun 2025 21:08:50 +0200 Subject: [PATCH] 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 --- docs/src/languages/rust.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/languages/rust.md b/docs/src/languages/rust.md index 9cd92471d1..ea6f6912cd 100644 --- a/docs/src/languages/rust.md +++ b/docs/src/languages/rust.md @@ -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": [] } } }