From: Felipe Contreras <firstname.lastname@example.org>
To: "brian m. carlson" <email@example.com>,
"Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>
Cc: Felipe Contreras <email@example.com>, firstname.lastname@example.org
Subject: Re: Man pages have colors? A deep dive into groff
Date: Mon, 17 May 2021 23:31:30 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
brian m. carlson wrote:
> On 2021-05-17 at 16:48:04, Ævar Arnfjörð Bjarmason wrote:
> > This looks much better.
> > I wonder a good follow-up (hint, hint! :) would be to have
> > exec_man_man() and exec_man_cmd() in builtin/help.c set this depending
> > on color.ui (so we'd do it by default with "auto").
> > Then e.g. "git help git" would look prettier than "man git".
> As I mentioned on the patch itself, I'd prefer if Git didn't do this. I
> have my own colors configured and don't want Git to render its man
> output differently from what I have.
> Even if I didn't, I wouldn't want Git to change the output of man(1)
> to be different from what's on the system.
That's a preference others don't share.
> I should point out that I have my shell configuration set up to use
> different colors depending on the capability of the terminal, such as
> using a 256-color palette when that's supported and a 16-color palette
> when it's not, so there is literally no configuration that Git can
> provide here that matches my existing settings.
Once again; your configuration is not going to be overridden.
> Additionally, colors tend to pose accessibility problems for a lot of
> people. I have normal color vision, but because I use a transparent
> background which renders as grey, the standard terminal red is nearly
> illegible for me. I also know people with colorblindness who have
> problems with various colors or any colors at all.
Their configuration won't be overridden either.
prev parent reply other threads:[~2021-05-18 4:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 22:10 Felipe Contreras
2021-05-17 16:48 ` Ævar Arnfjörð Bjarmason
2021-05-17 19:28 ` Junio C Hamano
2021-05-17 22:44 ` Felipe Contreras
2021-05-17 22:54 ` Randall S. Becker
2021-05-17 23:33 ` Felipe Contreras
2021-05-18 1:27 ` Junio C Hamano
2021-05-18 4:27 ` Felipe Contreras
2021-05-18 7:16 ` Jeff King
2021-05-18 13:21 ` Felipe Contreras
2021-05-18 14:27 ` Junio C Hamano
2021-05-18 1:28 ` brian m. carlson
2021-05-18 2:12 ` Junio C Hamano
2021-05-18 4:35 ` Felipe Contreras
2021-05-18 4:31 ` Felipe Contreras [this message]
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:
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 \
* 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 inbox:
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).