Skip to content

Commit 0dbbf14

Browse files
bors[bot]Veykril
andauthored
Merge #11042
11042: minor: clarify RA_LOG env var troubleshooting r=lnicola a=Veykril cc #10261 Co-authored-by: Lukas Wirth <[email protected]>
2 parents 4c68672 + dc92576 commit 0dbbf14

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/user/manual.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -447,7 +447,7 @@ If the date is more than a week ago, it's better to update rust-analyzer version
447447

448448
The next thing to check would be panic messages in rust-analyzer's log.
449449
Log messages are printed to stderr, in VS Code you can see then in the `Output > Rust Analyzer Language Server` tab of the panel.
450-
To see more logs, set the `RA_LOG=info` environment variable.
450+
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.
451451

452452
To fully capture LSP messages between the editor and the server, set `"rust-analyzer.trace.server": "verbose"` config and check
453453
`Output > Rust Analyzer Language Server Trace`.

0 commit comments

Comments
 (0)