2008-02-06 12:16:08 +00:00
|
|
|
|
#!/bin/sh
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2008 Timo Hirvonen
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
test_description='Test diff/status color escape codes'
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
|
|
color()
|
|
|
|
|
{
|
2010-02-28 02:56:38 +00:00
|
|
|
|
actual=$(git config --get-color no.such.slot "$1") &&
|
|
|
|
|
test "$actual" = "$2"
|
2008-02-06 12:16:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
invalid_color()
|
|
|
|
|
{
|
2010-02-28 02:56:38 +00:00
|
|
|
|
test_must_fail git config --get-color no.such.slot "$1"
|
2008-02-06 12:16:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
test_expect_success 'reset' '
|
|
|
|
|
color "reset" "[m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'attribute before color name' '
|
|
|
|
|
color "bold red" "[1;31m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'color name before attribute' '
|
|
|
|
|
color "red bold" "[1;31m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'attr fg bg' '
|
|
|
|
|
color "ul blue red" "[4;34;41m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'fg attr bg' '
|
|
|
|
|
color "blue ul red" "[4;34;41m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'fg bg attr' '
|
|
|
|
|
color "blue red ul" "[4;34;41m"
|
|
|
|
|
'
|
|
|
|
|
|
2010-02-28 02:56:38 +00:00
|
|
|
|
test_expect_success 'fg bg attr...' '
|
|
|
|
|
color "blue bold dim ul blink reverse" "[1;2;4;5;7;34m"
|
|
|
|
|
'
|
|
|
|
|
|
parse_color: recognize "no$foo" to clear the $foo attribute
You can turn on ANSI text attributes like "reverse" by
putting "reverse" in your color spec. However, you cannot
ask to turn reverse off.
For common cases, this does not matter. You would turn on
"reverse" at the start of a colored section, and then clear
all attributes with a "reset". However, you may wish to turn
on some attributes, then selectively disable others. For
example:
git log --format="%C(bold ul yellow)%h%C(noul) %s"
underlines just the hash, but without the need to re-specify
the rest of the attributes. This can also help third-party
programs, like contrib/diff-highlight, that want to turn
some attribute on/off without disrupting existing coloring.
Note that some attribute specifications are probably
nonsensical (e.g., "bold nobold"). We do not bother to flag
such constructs, and instead let the terminal sort it out.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-11-20 15:25:52 +00:00
|
|
|
|
# note that nobold and nodim are the same code (22)
|
|
|
|
|
test_expect_success 'attr negation' '
|
|
|
|
|
color "nobold nodim noul noblink noreverse" "[22;24;25;27m"
|
|
|
|
|
'
|
|
|
|
|
|
2010-02-28 02:56:38 +00:00
|
|
|
|
test_expect_success 'long color specification' '
|
|
|
|
|
color "254 255 bold dim ul blink reverse" "[1;2;4;5;7;38;5;254;48;5;255m"
|
|
|
|
|
'
|
|
|
|
|
|
parse_color: recognize "no$foo" to clear the $foo attribute
You can turn on ANSI text attributes like "reverse" by
putting "reverse" in your color spec. However, you cannot
ask to turn reverse off.
For common cases, this does not matter. You would turn on
"reverse" at the start of a colored section, and then clear
all attributes with a "reset". However, you may wish to turn
on some attributes, then selectively disable others. For
example:
git log --format="%C(bold ul yellow)%h%C(noul) %s"
underlines just the hash, but without the need to re-specify
the rest of the attributes. This can also help third-party
programs, like contrib/diff-highlight, that want to turn
some attribute on/off without disrupting existing coloring.
Note that some attribute specifications are probably
nonsensical (e.g., "bold nobold"). We do not bother to flag
such constructs, and instead let the terminal sort it out.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-11-20 15:25:52 +00:00
|
|
|
|
test_expect_success 'absurdly long color specification' '
|
|
|
|
|
color \
|
|
|
|
|
"#ffffff #ffffff bold nobold dim nodim ul noul blink noblink reverse noreverse" \
|
|
|
|
|
"[1;2;4;5;7;22;24;25;27;38;2;255;255;255;48;2;255;255;255m"
|
|
|
|
|
'
|
|
|
|
|
|
2015-01-20 22:14:48 +00:00
|
|
|
|
test_expect_success '0-7 are aliases for basic ANSI color names' '
|
|
|
|
|
color "0 7" "[30;47m"
|
|
|
|
|
'
|
|
|
|
|
|
2008-02-06 12:16:08 +00:00
|
|
|
|
test_expect_success '256 colors' '
|
|
|
|
|
color "254 bold 255" "[1;38;5;254;48;5;255m"
|
|
|
|
|
'
|
|
|
|
|
|
2014-11-20 15:25:39 +00:00
|
|
|
|
test_expect_success '24-bit colors' '
|
|
|
|
|
color "#ff00ff black" "[38;2;255;0;255;40m"
|
|
|
|
|
'
|
|
|
|
|
|
2014-11-20 15:16:09 +00:00
|
|
|
|
test_expect_success '"normal" yields no color at all"' '
|
|
|
|
|
color "normal black" "[40m"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success '-1 is a synonym for "normal"' '
|
|
|
|
|
color "-1 black" "[40m"
|
|
|
|
|
'
|
|
|
|
|
|
2008-02-06 12:16:08 +00:00
|
|
|
|
test_expect_success 'color too small' '
|
|
|
|
|
invalid_color "-2"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'color too big' '
|
|
|
|
|
invalid_color "256"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'extra character after color number' '
|
|
|
|
|
invalid_color "3X"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'extra character after color name' '
|
|
|
|
|
invalid_color "redX"
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'extra character after attribute' '
|
|
|
|
|
invalid_color "dimX"
|
|
|
|
|
'
|
|
|
|
|
|
ignore unknown color configuration
When parsing the config file, if there is a value that is
syntactically correct but unused, we generally ignore it.
This lets non-core porcelains store arbitrary information in
the config file, and it means that configuration files can
be shared between new and old versions of git (the old
versions might simply ignore certain configuration).
The one exception to this is color configuration; if we
encounter a color.{diff,branch,status}.$slot variable, we
die if it is not one of the recognized slots (presumably as
a safety valve for user misconfiguration). This behavior
has existed since 801235c (diff --color: use
$GIT_DIR/config, 2006-06-24), but hasn't yet caused a
problem. No porcelain has wanted to store extra colors, and
we once a color area (like color.diff) has been introduced,
we've never changed the set of color slots.
However, that changed recently with the addition of
color.diff.func. Now a user with color.diff.func in their
config can no longer freely switch between v1.6.6 and older
versions; the old versions will complain about the existence
of the variable.
This patch loosens the check to match the rest of
git-config; unknown color slots are simply ignored. This
doesn't fix this particular problem, as the older version
(without this patch) is the problem, but it at least
prevents it from happening again in the future.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-12-12 12:25:24 +00:00
|
|
|
|
test_expect_success 'unknown color slots are ignored (diff)' '
|
|
|
|
|
git config color.diff.nosuchslotwilleverbedefined white &&
|
|
|
|
|
git diff --color
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unknown color slots are ignored (branch)' '
|
|
|
|
|
git config color.branch.nosuchslotwilleverbedefined white &&
|
|
|
|
|
git branch -a
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'unknown color slots are ignored (status)' '
|
|
|
|
|
git config color.status.nosuchslotwilleverbedefined white || exit
|
|
|
|
|
git status
|
|
|
|
|
case $? in 0|1) : ok ;; *) false ;; esac
|
|
|
|
|
'
|
|
|
|
|
|
2008-02-06 12:16:08 +00:00
|
|
|
|
test_done
|