diff options
author | Matthieu Moy <Matthieu.Moy@imag.fr> | 2013-06-10 16:26:09 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-06-10 10:55:42 -0700 |
commit | 4c7f1819b3c142ace98269a556bc929c80e7c9fd (patch) | |
tree | 19e925c8df63a6b3cf7fccc1ec8e8a91ea0ea7d7 /git-merge-one-file.sh | |
parent | config: refactor management of color.ui's default value (diff) | |
download | tgif-4c7f1819b3c142ace98269a556bc929c80e7c9fd.tar.xz |
make color.ui default to 'auto'
Most users seem to like having colors enabled, and colors can help
beginners to understand the output of some commands (e.g. notice
immediately the boundary between commits in the output of "git log").
Many tutorials tell the users to set color.ui=auto as a very first step,
which tend to indicate that color.ui=none is not the recommanded value,
hence should not be the default.
These tutorials would benefit from skipping this step and starting the
real Git manipulations earlier. Other beginners do not know about
color.ui=auto, and may not discover it by themselves, hence live with
black&white outputs while they may have preferred colors.
A few people (e.g. color-blind) prefer having no colors, but they can
easily set color.ui=never for this (and googling "disable colors in git"
already tells them how to do so), but this needs not occupy space in
beginner-oriented documentations.
A transition period with Git emitting a warning when color.ui is unset
would be possible, but the discomfort of having the warning seems
superior to the benefit: users may be surprised by the change, but not
harmed by it.
The default value is changed, and the documentation is reworded to
mention "color.ui=false" first, since the primary use of color.ui after
this change is to disable colors, not to enable it.
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-merge-one-file.sh')
0 files changed, 0 insertions, 0 deletions