From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>,
git@vger.kernel.org
Subject: Re: Man pages have colors? A deep dive into groff
Date: Mon, 17 May 2021 23:35:25 -0500 [thread overview]
Message-ID: <60a3440d3f76e_14d1bc208ed@natae.notmuch> (raw)
In-Reply-To: <xmqqeee44wp4.fsf@gitster.g>
Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > 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.
> >
> > 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.
>
> git -c color.man=false help -m" would let you consume the output in
> any way you want, I would presume?
His configuration won't be overridden. He doesn't need to change
a thing.
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-18 4:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 22:10 Man pages have colors? A deep dive into groff 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 [this message]
2021-05-18 4:31 ` Felipe Contreras
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=60a3440d3f76e_14d1bc208ed@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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).