git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Anatoly Borodin <anatoly.borodin@gmail.com>
Date
Sep 16, 2016, 01:40 UTC
Message-ID
<nrfihd$a4o$1@blaine.gmane.org>
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.
           Defaults to false.

If the value false is the default, and neither color.branch nor color.ui is set in any config file, one can expect that

(1)	git branch
and
(2)	git config color.branch false ; git branch

produce the same result. But only (2) produces colorless output, (1) uses colors (that probably depend on the default value of color.ui).

The same story with color.diff and git-show, color.grep, etc.

Is it me being a non-native English speaker, or does this part really need to be rewritten?

PS git version 2.9.3
-- 
Mit freundlichen Grüßen,
Anatoly Borodin
Next: Matthieu Moy
Message 1 of 3 in “Potentially misleading color.* defaults explanation in git-config(1)”
  1. Anatoly BorodinSep 16, 2016
  2. Matthieu MoySep 16, 2016
  3. Anatoly BorodinSep 17, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.