Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2025-01-13 13:48:50 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update README

Browse source
This commit is contained in:
Alexander Ekdahl 2019-11-29 19:36:48 -05:00
parent eb4e70fc67
commit 1793abf4fd
1 changed files with 2 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/dev/README.md
View file

@ -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. figure out where logs go.
Inside rust-analyzer, we use the standard `log` crate for logging, and 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 `env_logger` for logging frontend. By default, log goes to stderr, but the
with `env_logger`), but the stderr itself is processed by VS Code. To mirror stderr itself is processed by VS Code.
logs to a `./log` directory, set `RA_LOG_DIR=1` environmental variable.
To see stderr in the running VS Code instance, go to the "Output" tab of the 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 panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that