Re: [PATCH v5] git-prompt: make colourization consistent
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 7, 2022, 16:04 UTC
- Message-ID
- <xmqq4k0w1mu7.fsf@gitster.g>
- In-Reply-To
- <466ec54a-825b-c3e6-e9f2-a7007af71b6d@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
Show 15 quoted lines
> On 6/5/22 02:26, Joakim Petersen wrote: >> If the user is in a sparse checkout, the sparsity state indicator >> follows a similar pattern to the short upstream state indicator. >> However, clearing colour of the colourized indicators changes how the >> sparsity state indicator is colourized , as it currently inherits (and >> before the change referenced also inherited) the colour of the last >> short state indicator before it. Reading the commit message of the >> change that introduced the sparsity state indicator, afda36dbf3b >> (git-prompt: include sparsity state as well, 2020-06-21), it appears >> this colourization also was unintended, so clearing the colour for said >> indicator further increases consistency. >> > > colourization? I have never heared that. Did you mean "colorization" (en-US) > or "colourisation" (en-UK)? I assumed the former.
;-)
Either way, that word is a mouthful. Using verb "to color" and "coloring" might be easier to read, perhaps?