-
Notifications
You must be signed in to change notification settings - Fork 221
preserve colors in diagnostics #1117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It might be enough to use |
Should that be a general concern for people who don’t have colors for whatever given reason? |
@shepmaster I make an effort to make sure that all output is readable as text only, but undoubtedly color makes the output easier to scan and reduces the likelihood of misreading things. In the screenshot, someone very knowledgeable mistook the |
note that this particular case is being fixed upstream in rustc: rust-lang/rust#132780 but it would be nice to fix it in the general case as well; it's never going to be possible to communicate as much information as visibly with text alone. |
I tried some time back making all suggestions have the verbose diff output in rust-lang/rust#127282. Landing that change or one like it will be a huge pain in the neck. |
The verbose "diff" suggestion format is easier to read, and the only one supported by annotate-snippets. Making verbose the default in one go would result in a huge PR that is too hard to land: rust-lang#127282. CC rust-lang/rust-playground#1117
The verbose "diff" suggestion format is easier to read, and the only one supported by annotate-snippets. Making verbose the default in one go would result in a huge PR that is too hard to land: rust-lang#127282. CC rust-lang/rust-playground#1117
rustc uses a lot of colors and highlighting in its errors. sometimes the output is hard to read when those are removed. consider for example this diagnostic, where it's hard to parse that the
-
is meant to be a highlight:it would be nice if playground preserved the colors.
repro here
The text was updated successfully, but these errors were encountered: