about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-12-18 20:21:29 +0000
committerGitHub <noreply@github.com>2021-12-18 20:21:29 +0000
commit0dbbf14bd6ba187b2dbbe38e51a691b387622d78 (patch)
tree9c2e8dc76b6655537c20a8b04fb3e581253d6fc0
parent4c686721c0fe4dd8fef74acb502c2327e0054dff (diff)
parentdc9257682c7fc2f663c0d49d4916788bc4a56ee8 (diff)
downloadrust-0dbbf14bd6ba187b2dbbe38e51a691b387622d78.tar.gz
rust-0dbbf14bd6ba187b2dbbe38e51a691b387622d78.zip
Merge #11042
11042: minor: clarify RA_LOG env var troubleshooting r=lnicola a=Veykril

cc https://github.com/rust-analyzer/rust-analyzer/pull/10261

Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
-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 cfcad7c66b7..1335f8df7c0 100644
--- a/docs/user/manual.adoc
+++ b/docs/user/manual.adoc
@@ -447,7 +447,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.
+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`.