about summary refs log tree commit diff
path: root/docs/dev
diff options
context:
space:
mode:
authorrezural <rezural@protonmail.com>2021-06-22 07:28:33 +1000
committerrezural <rezural@protonmail.com>2021-06-22 07:28:33 +1000
commitceeee5e3c6e2ab24d6d83a1e000780da537c1507 (patch)
tree673f023be6865a67b471e92a8ebd0e4df764f1b0 /docs/dev
parentbaa060a9947f0006a256acdac075691da4168edf (diff)
downloadrust-ceeee5e3c6e2ab24d6d83a1e000780da537c1507.tar.gz
rust-ceeee5e3c6e2ab24d6d83a1e000780da537c1507.zip
add documentation of RA_LOG_FILE
Diffstat (limited to 'docs/dev')
-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 e81f1e74c38..a394b85010c 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
 
 Inside rust-analyzer, we use the standard `log` crate for logging, and `env_logger` for logging frontend.
 By default, log goes to stderr, but the stderr itself is processed by VS Code.
-`--log-file <PATH>` CLI argument allows logging to file.
+`--log-file <PATH>` CLI argument allows logging to file. 
+Setting the `RA_LOG_FILE=<PATH>` environment variable will also log to file, it will also override `--log-file`.
 
 To see stderr in the running VS Code instance, go to the "Output" tab of the panel and select `rust-analyzer`.
 This shows `eprintln!` as well.