aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index e81f1e74c..a394b8501 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -131,7 +131,8 @@ Logging is done by both rust-analyzer and VS Code, so it might be tricky to figu
131 131
132Inside rust-analyzer, we use the standard `log` crate for logging, and `env_logger` for logging frontend. 132Inside rust-analyzer, we use the standard `log` crate for logging, and `env_logger` for logging frontend.
133By default, log goes to stderr, but the stderr itself is processed by VS Code. 133By default, log goes to stderr, but the stderr itself is processed by VS Code.
134`--log-file <PATH>` CLI argument allows logging to file. 134`--log-file <PATH>` CLI argument allows logging to file.
135Setting the `RA_LOG_FILE=<PATH>` environment variable will also log to file, it will also override `--log-file`.
135 136
136To see stderr in the running VS Code instance, go to the "Output" tab of the panel and select `rust-analyzer`. 137To see stderr in the running VS Code instance, go to the "Output" tab of the panel and select `rust-analyzer`.
137This shows `eprintln!` as well. 138This shows `eprintln!` as well.