about summary refs log tree commit diff
path: root/docs/dev
diff options
context:
space:
mode:
authorAlexander Ekdahl <alexander@ekdahl.io>2019-11-29 19:36:48 -0500
committerAlexander Ekdahl <alexander@ekdahl.io>2019-11-29 19:36:48 -0500
commit1793abf4fd1382a8b9bae798139aaebdc33b673e (patch)
treebaa17a934af68618e599547028fc9f8f4d25222f /docs/dev
parenteb4e70fc676a97a7b411f372be1727df51a8906a (diff)
downloadrust-1793abf4fd1382a8b9bae798139aaebdc33b673e.tar.gz
rust-1793abf4fd1382a8b9bae798139aaebdc33b673e.zip
Update README
Diffstat (limited to 'docs/dev')
-rw-r--r--docs/dev/README.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 0f64d7e5f8c..2f6215d6bb4 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -124,9 +124,8 @@ Logging is done by both rust-analyzer and VS Code, so it might be tricky to
 figure out where logs go.
 
 Inside rust-analyzer, we use the standard `log` crate for logging, and
-`flexi_logger` for logging frotend. By default, log goes to stderr (the same as
-with `env_logger`), but the stderr itself is processed by VS Code. To mirror
-logs to a `./log` directory, set `RA_LOG_DIR=1` environmental variable.
+`env_logger` for logging frontend. By default, log goes to stderr, but the
+stderr itself is processed by VS Code.
 
 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. Note that