Re: Potentially misleading color.* defaults explanation in git-config(1)

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Sep 16, 2016, 07:25 UTC
Message-ID: <vpqeg4k1f3g.fsf@anie.imag.fr>
In-Reply-To: <nrfihd$a4o$1@blaine.gmane.org>

Anatoly Borodin <anatoly.borodin@gmail.com> writes:

Show 8 quoted lines

> Hi All!
>
> git-config(1) says:
>
>        color.branch
>            A boolean to enable/disable color in the output of git-branch(1).
>            May be set to always, false (or never) or auto (or true), in which
>            case colors are used only when the output is to a terminal.

So far, so good.

>            Defaults to false.

The truth is: Defaults to following color.ui, which used to default to false but now defaults to auto.

My bad, I forgot to update these parts of the docs when changing the default for color.ui (a while back already). Patch follows.

> (2)	git config color.branch false ; git branch

Unrelated from the question, but you could write

git -c color.branch=false git branch

to set a configuration value just for one command.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/