On 21/05/2021 21:48, Igor Djordjevic wrote:
>
> So, the whole point is make the default value be "no color" for each
> and every application consistently, where user (and _not_ developer)
> needs to opt-in in order to enable colors (in each and every
> application where colors are in fact still desired).
Oh, and might be what NO_COLOR homepage provides as a tip for
"disabling color in software not supporting NO_COLOR" for Git
specifically might be a good (and enough of a) clue by itself...?
git config --global color.ui false
So I'd argue that Git should react to NO_COLOR exactly as it should
react to `color.ui` set to false - disabling all color.
Do note it's only by default, in case no (other) color configuration is
specified - any existing user config should take precedence, of course,
further acting as per user's desire ("... NO_COLOR says I prefer no
color in general, but I do want color in this specific case, enabled by
setting this software specific config option explicitly...").
