summaryrefslogtreecommitdiff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-01-09 17:07:35 +0000
committerbors <bors@rust-lang.org>2023-01-09 17:07:35 +0000
commit368e0bb32f1178cf162c2ce5f7e10b7ae211eb26 (patch)
treec55fc1d7b528679b40aa5cd0abd3cd905ee81715 /tests/rustdoc-js-std/parser-errors.js
parentf32e20edb99a15d42984ec89f6b3986248845929 (diff)
parent283dfc45dd8fb1e6bbe78c8b2e90cb5d543f2f06 (diff)
downloadrust-368e0bb32f1178cf162c2ce5f7e10b7ae211eb26.tar.gz
Auto merge of #13848 - ian-h-chamberlain:feature/color-compiler-diagnostics, r=ian-h-chamberlain
Colorize `cargo check` diagnostics in VSCode via text decorations Fixes #13648 ![colored-rustc-diagnostics](https://user-images.githubusercontent.com/11131775/209479884-10eef8ca-37b4-4aae-88f7-3591ac01b25e.gif) Use ANSI control characters to display text decorations matching the VScode terminal theme, and strip them out when providing text content for rustc diagnostics. This adds the small [`anser`](https://www.npmjs.com/package/anser) library (MIT license, no dependencies) to parse the control codes, and it also supports HTML output so it should be fairly easy to switch to a rendered HTML/webview implementation in the future I also updated the default `cargo check` command to use the rendered ANSI diagnostics, although I'm not sure if it makes sense to put this kind of thing behind a feature flag, or whether it might have any issues on Windows (as I believe ANSI codes are not used for colorization there)?
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions