Different error output style

[ShenMian]

Problem

Different error output style(color, first letter case). I think this may not be intentional?

Steps

No response

Possible Solution(s)

Unify the error output style.

Notes

No response

Version

cargo 1.62.0 (a748cf5a3 2022-06-08)
release: 1.62.0
commit-hash: a748cf5a3e666bc2dcdf54f37adef8ef22196452
commit-date: 2022-06-08
host: x86_64-pc-windows-msvc
libgit2: 1.4.2 (sys:0.14.2 vendored)
libcurl: 7.80.0-DEV (sys:0.4.51+curl-7.80.0 vendored ssl:Schannel)
os: Windows 10.0.22621 (Windows 10 Pro) [64-bit]

[epage]

cargo implements its own subcommand dispatching and is trying to emulate clap's error to be consistent. Looks like we've ended up diverging in whether : is colored. I lean towards clap's approach (e.g. I tend to bold my : with terms) but I can go either way.

[SummerGram]

Hi, Can I take this one?

[epage]

Hi, Can I take this one?

For the :, it depends on which is preferred. I gave my opinion but unsure how much of a "right answer" this is and which direction we officially want to go.

As for the capitalization, clap v4.1 changed the message to be lower case and we've upgraded to it.

[SummerGram]

For the :, it depends on which is preferred. I gave my opinion but unsure how much of a "right answer" this is and which direction we officially want to go.

Can we make the error output style consistent? If it needs 2 styles, then it can provide a way for users choose.

[epage]

My assumption is we would make it consistent. The question is whether we should change clap or cargo.

[epage]

Hmm, looked at this again and there are three sources of ::

• rustc
• cargo
• clap

We'd need a decision across all three