git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: "Phillip Wood" <phillip.wood123@gmail.com>,
	"Felipe Contreras" <felipe.contreras@gmail.com>,
	git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Leah Neukirchen" <leah@vuxu.org>,
	"Randall S. Becker" <rsbecker@nexbridge.com>
Subject: Re: [PATCH v4] help: colorize man pages
Date: Fri, 21 May 2021 13:01:35 -0500	[thread overview]
Message-ID: <60a7f57fe3301_5503920831@natae.notmuch> (raw)
In-Reply-To: <YKdy5jhHgG2who27@coredump.intra.peff.net>

Jeff King wrote:
> On Fri, May 21, 2021 at 02:06:48PM +0900, Junio C Hamano wrote:
> 
> > Phillip Wood <phillip.wood123@gmail.com> writes:
> > 
> > > On 20/05/2021 05:07, Felipe Contreras wrote:
> > >> We already colorize tools traditionally not colorized by default, like
> > >> diff and grep. Let's do the same for man.
> > >
> > > I think there is a distinction between 'diff' and 'grep' where we are
> > > generating the content and help where we are running man - I would 
> > > expect a man page to look the same whether it is displayed by 'man git
> > > foo' or 'git help foo'
> > 
> > ... as long as the user chooses "man" backend, that is.  And I tend
> > to agree, but that is our expectation.
> > 
> > If we added this new mode of driving the same "man" but with
> > different environment variables exported to tweak how "less"
> > behaves, and taught it to builtin/help.c::exec_viewer() and
> > builtin/help.c::man_viewer_list, that might become more palatable in
> > the sense that we can view it as feeding the same manual page to
> > this another "man" that behaves differently from the plain "man",
> > just like we can feed it to "woman" or "konqueror" to get a different
> > view.  So those (like you and I) who expect a man page to look the
> > same in "man git foo" and "git help -m foo" can keep using our current
> > configuration, while those who want yet another variant of "man" output
> > in addition to the current "man", "woman", and "konqueror" can choose
> > it and get "colorized" output.
> 
> I still don't understand what we gain by making this a Git feature,

What do we gain by making `git diff` output color?

> Why would we do that versus saying: if you want to change the colors in
> the tool that Git calls, then configure the tool?

Once again... How?

> If you like to see colors in manpages, why not configure "man" (either
> by setting these environment variables all the time, or by triggering
> them in MANPAGER)?

Let me try that...

  MANPAGER="less -Dd+r -Du+b -Ds+m" git help git

It doesn't work.

> If those configurations are awkward to trigger via man (e.g., putting
> escapes into termcap variables), isn't that something that could be
> improved in man? And then it would benefit everyone who uses man, not
> just Git.

Sure. In the meantime let's make `git help` output with color just like
`git diff`.

Cheers.

(and good luck convincing a GNU project of anything)

-- 
Felipe Contreras

  reply	other threads:[~2021-05-21 18:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  4:07 [PATCH v4] help: colorize man pages Felipe Contreras
2021-05-20  9:26 ` Phillip Wood
2021-05-20 13:58   ` Felipe Contreras
2021-05-20 15:13     ` Phillip Wood
2021-05-20 15:59       ` Felipe Contreras
2021-05-20 18:00         ` Phillip Wood
2021-05-21 17:43           ` Felipe Contreras
2021-05-21  5:06   ` Junio C Hamano
2021-05-21  8:44     ` Jeff King
2021-05-21 18:01       ` Felipe Contreras [this message]
2021-05-21 20:26         ` Jeff King
2021-05-21 21:40           ` Felipe Contreras
2021-05-22  9:55             ` Jeff King
2021-05-22 12:43               ` Philip Oakley
2021-05-22 20:53                 ` Felipe Contreras
2021-05-22 20:49               ` Felipe Contreras
2021-05-21 17:54     ` Felipe Contreras
2021-05-20 14:39 ` Leah Neukirchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60a7f57fe3301_5503920831@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=leah@vuxu.org \
    --cc=peff@peff.net \
    --cc=phillip.wood123@gmail.com \
    --cc=rsbecker@nexbridge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).