{"thread":{"id":"44096","subject":"Potentially misleading color.* defaults explanation in git-config(1)","startedAt":"2016-09-16T01:40:31Z","lastAt":"2016-09-17T08:17:36Z","messageCount":3,"participants":["Anatoly Borodin","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"302045","messageId":"nrfihd$a4o$1@blaine.gmane.org","threadId":"44096","inReplyTo":null,"subject":"Potentially misleading color.* defaults explanation in git-config(1)","fromName":"Anatoly Borodin","fromEmail":"anatoly.borodin@gmail.com","sentAt":"2016-09-16T01:40:01Z","receivedAt":"2016-09-16T01:40:31Z","isPatch":false,"sender":{"key":"anatoly.borodin@gmail.com","avatar":"https://gravatar.com/avatar/59f11f1f45cf5ebb7bcca8da94b43cfe5f596d91c0a3e27ad0d2a861cc2bbce7?d=mp&s=160"},"body":"Hi All!\n\ngit-config(1) says:\n\n       color.branch\n           A boolean to enable/disable color in the output of git-branch(1).\n           May be set to always, false (or never) or auto (or true), in which\n           case colors are used only when the output is to a terminal.\n           Defaults to false.\n\nIf the value false is the default, and neither color.branch nor\ncolor.ui is set in any config file, one can expect that\n\n(1)\tgit branch\n\nand\n\n(2)\tgit config color.branch false ; git branch\n\nproduce the same result. But only (2) produces colorless output, (1)\nuses colors (that probably depend on the default value of color.ui).\n\nThe same story with color.diff and git-show, color.grep, etc.\n\nIs it me being a non-native English speaker, or does this part really\nneed to be rewritten?\n\nPS git version 2.9.3\n\n-- \nMit freundlichen Grüßen,\nAnatoly Borodin\n\n"},{"id":"302047","messageId":"vpqeg4k1f3g.fsf@anie.imag.fr","threadId":"44096","inReplyTo":"nrfihd$a4o$1@blaine.gmane.org","subject":"Re: Potentially misleading color.* defaults explanation in git-config(1)","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2016-09-16T07:25:07Z","receivedAt":"2016-09-16T07:25:18Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Anatoly Borodin <anatoly.borodin@gmail.com> writes:\n\n> Hi All!\n>\n> git-config(1) says:\n>\n>        color.branch\n>            A boolean to enable/disable color in the output of git-branch(1).\n>            May be set to always, false (or never) or auto (or true), in which\n>            case colors are used only when the output is to a terminal.\n\nSo far, so good.\n\n>            Defaults to false.\n\nThe truth is: Defaults to following color.ui, which used to default to\nfalse but now defaults to auto.\n\nMy bad, I forgot to update these parts of the docs when changing the\ndefault for color.ui (a while back already). Patch follows.\n\n> (2)\tgit config color.branch false ; git branch\n\nUnrelated from the question, but you could write\n\ngit -c color.branch=false git branch\n\nto set a configuration value just for one command.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"302099","messageId":"nriu5n$uss$1@blaine.gmane.org","threadId":"44096","inReplyTo":"vpqeg4k1f3g.fsf@anie.imag.fr","subject":"Re: Potentially misleading color.* defaults explanation in git-config(1)","fromName":"Anatoly Borodin","fromEmail":"anatoly.borodin@gmail.com","sentAt":"2016-09-17T08:16:55Z","receivedAt":"2016-09-17T08:17:36Z","isPatch":false,"sender":{"key":"anatoly.borodin@gmail.com","avatar":"https://gravatar.com/avatar/59f11f1f45cf5ebb7bcca8da94b43cfe5f596d91c0a3e27ad0d2a861cc2bbce7?d=mp&s=160"},"body":"Hi!\n\nMatthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:\n> My bad, I forgot to update these parts of the docs when changing the\n> default for color.ui (a while back already). Patch follows.\n\nThanks for the patch!\n\n> git -c color.branch=false git branch\n\nOh, that's a nice one! I don't get a chance to use those\nbetween-git-and-command options often.\n\nMerci!\n\n-- \nMit freundlichen Grüßen,\nAnatoly Borodin\n\n"}]}