document behavior of empty color name
Commit 55cccf4bb (color_parse_mem: allow empty color spec, 2017-02-01) clearly defined the behavior of an empty color config variable. Let's document that, and give a hint about why it might be useful. It's important not to say that it makes the item uncolored, because it doesn't. It just sets no attributes, which means that any previous attributes continue to take effect. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Feb 2, 2017 at 13:42 UTC
512aba261a8951a470147b493c720f205638ba14
1 file changed
+3
Documentation/config.txt
+3
@@ -170,6 +170,9 @@ The position of any attributes with respect to the colors
170
be turned off by prefixing them with `no` or `no-` (e.g., `noreverse`,
171
`no-ul`, etc).
172
+
173
+An empty color string produces no color effect at all. This can be used
174
+to avoid coloring specific elements without disabling color entirely.
175
++
176
For git's pre-defined color slots, the attributes are meant to be reset
177
at the beginning of each item in the colored output. So setting
178
`color.decorate.branch` to `black` will paint that branch name in a