diff options
author | Alexander Ekdahl <[email protected]> | 2019-11-30 00:36:48 +0000 |
---|---|---|
committer | Alexander Ekdahl <[email protected]> | 2019-11-30 00:36:48 +0000 |
commit | 1793abf4fd1382a8b9bae798139aaebdc33b673e (patch) | |
tree | baa17a934af68618e599547028fc9f8f4d25222f /docs | |
parent | eb4e70fc676a97a7b411f372be1727df51a8906a (diff) |
Update README
Diffstat (limited to 'docs')
-rw-r--r-- | docs/dev/README.md | 5 |
1 files changed, 2 insertions, 3 deletions
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 | |||
124 | figure out where logs go. | 124 | figure out where logs go. |
125 | 125 | ||
126 | Inside rust-analyzer, we use the standard `log` crate for logging, and | 126 | Inside rust-analyzer, we use the standard `log` crate for logging, and |
127 | `flexi_logger` for logging frotend. By default, log goes to stderr (the same as | 127 | `env_logger` for logging frontend. By default, log goes to stderr, but the |
128 | with `env_logger`), but the stderr itself is processed by VS Code. To mirror | 128 | stderr itself is processed by VS Code. |
129 | logs to a `./log` directory, set `RA_LOG_DIR=1` environmental variable. | ||
130 | 129 | ||
131 | To see stderr in the running VS Code instance, go to the "Output" tab of the | 130 | To see stderr in the running VS Code instance, go to the "Output" tab of the |
132 | panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that | 131 | panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that |