From 1793abf4fd1382a8b9bae798139aaebdc33b673e Mon Sep 17 00:00:00 2001 From: Alexander Ekdahl Date: Fri, 29 Nov 2019 19:36:48 -0500 Subject: Update README --- docs/dev/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/dev') diff --git a/docs/dev/README.md b/docs/dev/README.md index 0f64d7e5f..2f6215d6b 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 -- cgit v1.2.3