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

Re: [PATCH] doc: explain the use of color.pager

From
Jeff King <peff@peff.net>
Date
May 20, 2021, 08:33 UTC
Message-ID
<YKYe9PZbTO1CyBOp@coredump.intra.peff.net>
In-Reply-To
<xmqq5yzdvrlg.fsf@gitster.g>
On Thu, May 20, 2021 at 03:36:59PM +0900, Junio C Hamano wrote:
Show 20 quoted lines
> > More importantly, I think I'd find a
> > reference to the commit or a quotation from the affected user more
> > helpful than a reference to the mailing list archive, since that would
> > make this a bit more self-contained.
> 
> The original commit and its log message we ended up with did not
> explain the motivation behind well enough.
> 
> The motivation from the original thread:
> 
>       When I use a pager that escapes the escape character or highlights the
>       content itself the output of git diff without the pager should have
>       colors but not with the pager.  For example using git diff with a
>       pathspec is quite short most of the time.  For git diff I have to
>       enable paging manually and run git diff | $PAGER usually but git log
>       uses the pager automatically and should not use colors with it.
> 
> can be quoted as a whole, but "the point is to deal with ..." is a
> succinct summary that is good enough for the purpose of this commit,
> I would think.
Thanks, I was just preparing a near-identical response.

I do think it's an important principle in general to summarize the content of things we link to. It's just that the summary in this case was so short that it was easy to look past. :)

Show 10 quoted lines
> > If I understood correctly, how about some text like the following?
> >
> > 	A boolean to specify whether `auto` color modes should colorize
> > 	output going to a pager, in addition to their behavior of
> > 	colorizing output going to a terminal. Defaults to true; [etc]
> 
> The variable has no control over what happens to output that
> directly goes to a terminal, so while the additional phrase might
> not be technically wrong per-se, I do not see why this is more clear
> than the original.

Unsurprisingly, that's my opinion, too. While writing it, I actually did try some longer explanations to explain from the ground up, but I worried it was distracting from the main point of this variable. E.g., something like:

  When color mode options (e.g., `color.ui`) are set to `auto`, Git by
  default will enable color when the output is going to a terminal or to
  a pager (since the pager itself is outputting to a terminal). This is
  a problem if your pager doesn't faithfully relay the color codes to
  the terminal. You can set this boolean to `false` to disable color
  when output is going to a terminal.
> So, in short, I think it would be sufficient to amend the proposed
> log message with s/deal with/to deal with/ and nothing else.
I'm happy with that.
-Peff
Previous: Junio C HamanoNext: Jonathan Nieder
Message 7 of 8 in “doc: explain the use of color.pager”
  1. doc: explain the use of color.pagerJeff King, May 19, 2021
  2. Felipe ContrerasMay 19, 2021
  3. Jonathan NiederMay 19, 2021
  4. Felipe ContrerasMay 19, 2021
  5. Junio C HamanoMay 19, 2021
  6. Junio C HamanoMay 20, 2021
  7. Jeff KingMay 20, 2021
  8. Jonathan NiederMay 20, 2021

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.