Re: Please, paint new branch errors in RED (or any visible color)

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Dec 12, 2021, 19:01 UTC
Message-ID: <211212.86o85labj1.gmgdl@evledraar.gmail.com>
In-Reply-To: <xmqq4k7dlld3.fsf@gitster.g>

On Sun, Dec 12 2021, Junio C Hamano wrote:

Show 11 quoted lines

> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> On Fri, Dec 10 2021, Jose Wielandt wrote:
>>
>>> Yes, I git switch has the same behavior.
>>> I also agree that add hints could be a good idea.
>>
>> I'll pick up this topic.
>
> Please make sure color challenged users can configure it away or
> customize it somehow.

Yes, I think it's a bug if we add any such coloring that isn't configurable via the usual color.* configuration. Although in this case it's usage.c. So perhaps "color.usage" (as in usage.c). But that squats on any future hypothetical "git usage". So maybe "color.coreUsage" (a "color.core.usage" would squat on any future "color.core.usage.<slot>" (i.e. there's no 4-level keys)>

> Making it opt-in is even better, but it is my personal taste.

*nod*. I'll see how it turns out. FWIW I think that it's probably too over-colored to do:

    <RED>fatal: the message</RED>

And it's probably better to just do:

    <RED>fatal</RED>: the message

But I'll see once we have actual examples. The advice output is fully-colored now. I.e. "hint: message", not just the "hint" part...