Michał Borejszo

Same issue happens on CLI tool, but probably needs another issue - the reason lies elsewhere.

WSL2 still has problems running: ``` ~/source/repos/flamegraph   master  target/release/flamegraph ls Cargo.lock LICENSE-APACHE README.md example.svg flamegraph.svg perf.data.old target Cargo.toml LICENSE-MIT bors.toml example_cropped.png perf.data src [ perf record: Woken...

Running into the same issue, `env_logger` is properly rendered in poor old `cmd.exe`, but `tracing_subscriber` prints out the ansi literals.. 

Interesting thing is that running the same app with `cargo run` gives proper behavior in windows console host, but running the built executable from `target` folder gives this buggy behavior....

So.. this seems more complicated. I definitely can reproduce the issue using `nu-ansi-term` v0.46, using their examples, but can not replicate using v0.47. That's why I assumed bumping the dependency...

Turns out, the real culprit is that `ENABLE_VIRTUAL_TERMINAL_PROCESSING` console mode is **not** set by default for windows legacy console host. See more details in this SO answer: https://superuser.com/a/1300251 It seems...

This seems unrelated to rust-analyzer itself, the thing is, using stable rust a project referencing rustix will fail with this error on `cargo check` (or `cargo clippy`), but build fine...

Looks like this can be finished & merged once `error_in_core` gets stabilized. https://github.com/rust-lang/rust/issues/103765