git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH v6] help: colorize man pages
Date: Tue, 08 Jun 2021 12:48:15 -0500	[thread overview]
Message-ID: <60bfad5f170df_1abb47208c1@natae.notmuch> (raw)
In-Reply-To: <xmqq4ke8pig9.fsf@gitster.g>

Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> 
> > I've been running with this on my personal git build since May 26th. I
> > haven't had any issues with it, and I like the new coloring.
> > ...
> > I think this is a good example of a change that we're better off just
> > merging down and then reverting if the wider audience of git users hates
> > it, rather than trying to come to some perfect consensus here
> > on-list.
> 
> My impression was tht we already had a rough consensus here on-list
> that it may be good to educate users who like this "new coloring"
> like you do to configure their "less",

Not true.

Jeff said users would probably have configured man to use colors
themselves, but he never responded back when I asked him *how* [1].

It is a tricky question, because I already know it's not possible to do
it in a way that works in all distributions, for all programs without
polluting the user environment to do things she probably doesn't want.

> so that they consistently get the "new coloring" they like whether
> they are doing "git help git", "man git", or even "man ls", and the
> approach the posted patch takes will not help (it only affects "git
> help git" among these).

Please explain exactly *how* the user will be able to do that.


Moreover. I don't think git should be in the business of educating users
how to use other software. The way they use less in conjunction with
other software is up to them.

And in fact we already help naive users that have not configured their
pager, so that it works better in git.

We do this for them:

  LESS=FRX LV=-c # see PAGER_ENV

Why aren't we "educating them" about LESS=FRX instead?

We have set good defaults for less since pretty much the start:

  f67b45f862 (Introduce trivial new pager.c helper infrastructure, 2006-02-28)


I don't think Jeff is the consensus. He expressed an opinion that
perhaps X is better, but without clearly defining X, that's not really
a viable option.

> I'd rather not to take it.

Can you explain why? All the outstanding comments have been addressed.

Cheers.

[1] https://lore.kernel.org/git/60a96e76a4b20_857e92085c@natae.notmuch/

-- 
Felipe Contreras

  reply	other threads:[~2021-06-08 17:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  5:44 [PATCH v6] help: colorize man pages Felipe Contreras
2021-05-24 13:13 ` Phillip Wood
2021-05-24 16:56   ` Felipe Contreras
2021-06-08 12:35 ` Ævar Arnfjörð Bjarmason
2021-06-08 13:57   ` Junio C Hamano
2021-06-08 17:48     ` Felipe Contreras [this message]
2021-06-21  8:34     ` [PATCH v7] help: colorize man pages if man.color=true under less(1) Ævar Arnfjörð Bjarmason
2021-06-21 10:17       ` Phillip Wood
2021-06-21 10:28       ` Junio C Hamano
2021-06-21 18:41         ` Felipe Contreras
2021-06-21 19:08         ` Ævar Arnfjörð Bjarmason
2021-06-23 23:58           ` Jeff King
2021-06-24  1:03             ` Felipe Contreras
2021-06-28 17:37             ` Junio C Hamano
2021-06-28 18:05               ` Felipe Contreras
2021-06-21 15:59       ` Felipe Contreras
2021-06-24  0:08       ` Jeff King
2021-06-29  1:42         ` Junio C Hamano
2021-06-29  1:48           ` Felipe Contreras
2021-06-24  1:44 ` [PATCH v6] help: colorize man pages Felipe Contreras
2021-06-26  2:50 ` [PATCH v8] help: add option to colorize man pages under less Felipe Contreras
2021-06-26 14:49   ` Ævar Arnfjörð Bjarmason

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=60bfad5f170df_1abb47208c1@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=phillip.wood123@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).