-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Open
Labels
A-console-outputArea: Terminal output, colors, progress bar, etc.Area: Terminal output, colors, progress bar, etc.C-bugCategory: bugCategory: bugS-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Description
Problem
Cargo and rustc are not consistent in terms of how they are coloring errors on the terminal.
Steps
- Run
cargo check
on a project with build failures.
As you can see, the two "error" are using two different shades of red. In terms of the colorize
crate, rustc is using bright_red
and cargo is using red
.
Possible Solution(s)
One of cargo or rustc should switch to the other tone of red. I have a slight preference for "bright red", that's why I reported this as a cargo issue.
Notes
No response
Version
$ cargo version --verbose
cargo 1.72.0 (103a7ff2e 2023-08-15)
release: 1.72.0
commit-hash: 103a7ff2ee7678d34f34d778614c5eb2525ae9de
commit-date: 2023-08-15
host: x86_64-unknown-linux-gnu
libgit2: 1.6.4 (sys:0.17.2 vendored)
libcurl: 8.1.2-DEV (sys:0.4.63+curl-8.1.2 vendored ssl:OpenSSL/1.1.1u)
ssl: OpenSSL 1.1.1u 30 May 2023
os: Debian n/a (trixie) [64-bit]
Metadata
Metadata
Assignees
Labels
A-console-outputArea: Terminal output, colors, progress bar, etc.Area: Terminal output, colors, progress bar, etc.C-bugCategory: bugCategory: bugS-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
weihanglo commentedon Sep 26, 2023
Thanks for the report!
We're aware of this and have #12627 for tracking one of the approach. See also #2290 (comment) for a short summary.
I lean to waiting for #12627 but also fine with manual tweaks.
weihanglo commentedon Sep 26, 2023
Without investigating it by myself, do you know since which version this happened, or it has been there for a while?
RalfJung commentedon Sep 26, 2023
I have no idea. I only just realized this when working on the messages for ui_test. It might have been like this for a while, it might have been hidden by me using a different terminal/configuration, it might be recent.
RalfJung commentedon Sep 26, 2023
I went back through time a bit -- this is definitely a very long-standing issue. I see the difference even with Rust 1.40.
epage commentedon Sep 26, 2023
Glad to see this wasn't something I broke recently as I've been making changes to how we do styling :)
#12578 added styling to clap and #12655 made us use shared definitions to ensure we'd stay in sync which also made our style choices easier to audit.
Cargo uses bold+red and a lot of has likely haven't noticed the discrepancy because bold+red gets colored the same as bright_red in a lot of themes.
epage commentedon Sep 26, 2023
We should probably do an audit of all colors used with their intended use and see where it'd work best to align.
Note that as follow ups to #12578 and #12655, cargo-fmt and cargo-clippy were also updated to align with cargo. I'm tempted to do this also to rustup but they hadn't upgrade to clap v4 last I checked.
rami3l commentedon Sep 26, 2023
@epage Oh we have just done that! (Thanks @djc for your rust-lang/rustup#3444!)
rustc
style errors for manifest parsing #13172Auto merge of #13172 - Muscraft:diagnostic-system, r=epage
Auto merge of #13172 - Muscraft:diagnostic-system, r=epage