about summary refs log tree commit diff
diff options
context:
space:
mode:
authorLukas Wirth <lukastw97@gmail.com>2021-12-18 21:02:03 +0100
committerGitHub <noreply@github.com>2021-12-18 21:02:03 +0100
commitdc9257682c7fc2f663c0d49d4916788bc4a56ee8 (patch)
tree5d606851bb45f056abea1d2e37720760c0b6efe2
parent1cd40a408ae7fca3d286667360e46c530034c3ff (diff)
downloadrust-dc9257682c7fc2f663c0d49d4916788bc4a56ee8.tar.gz
rust-dc9257682c7fc2f663c0d49d4916788bc4a56ee8.zip
Fix typo
-rw-r--r--docs/user/manual.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc
index c0d12851481..0be1959a5e1 100644
--- a/docs/user/manual.adoc
+++ b/docs/user/manual.adoc
@@ -445,7 +445,7 @@ If the date is more than a week ago, it's better to update rust-analyzer version
 
 The next thing to check would be panic messages in rust-analyzer's log.
 Log messages are printed to stderr, in VS Code you can see then in the `Output > Rust Analyzer Language Server` tab of the panel.
-To see more logs, set the `RA_LOG=info` environment variable, this can be done either by setting the environment variable manually or by using `rust-analyzer.rust-analyzer.server.extraEnv`, note that both of these approaches require the server to be restarted.
+To see more logs, set the `RA_LOG=info` environment variable, this can be done either by setting the environment variable manually or by using `rust-analyzer.server.extraEnv`, note that both of these approaches require the server to be restarted.
 
 To fully capture LSP messages between the editor and the server, set `"rust-analyzer.trace.server": "verbose"` config and check
 `Output > Rust Analyzer Language Server Trace`.