Re: [PATCH] Give the hunk comment its own color
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 18, 2009, 21:56 UTC
- Message-ID
- <7vaayjebu5.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20091118142320.GA1220@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> PS I almost complained about your default of "magenta" as the same as > the meta color before I remembered that magenta meta is a personal > setting I use.
On black-on-white terminals, cyan tends to be less visible, and I think that is the whole point of painting the hunk header @@ .. @@ in that color--- make it less distracting).
But the function name on the line is not something that should be made less visible---if that part of the line were a meaningless cruft, we wouldn't have configurable funcname patterns after all.
I would suggest "normal" as the neutral default. After all, the purpose of the funcname in the hunk header is to give context to people who read patches.
> I'm not sure what is the best way to arrive at a default color for > something like this. Arguing about it really is almost the definition of > bikeshedding. Maybe next year's git survey should contain a special > section on colors, and majority should rule. :)
Sorry, but this is no democracy ;-)