From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Felipe Contreras'" <felipe.contreras@gmail.com>,
"'Junio C Hamano'" <gitster@pobox.com>,
"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: Man pages have colors? A deep dive into groff
Date: Mon, 17 May 2021 18:54:54 -0400 [thread overview]
Message-ID: <00b701d74b6f$aa295ed0$fe7c1c70$@nexbridge.com> (raw)
In-Reply-To: <60a2f1c4cab0d_13c3702083a@natae.notmuch>
On May 17, 2021 6:44 PM, Felipe Contreras wrote:
>Junio C Hamano wrote:
>> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>>
>> > 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 long as color.man.ui can be used to override the blanket color.ui,
>> I think it is a good idea.
>
>Why not use color.pager?
I think there is a lesson to be learned from git checkout; specifically not to overload semantics. Manual representation is a presentation world unto itself that has should not be blended with programs like less. More than that, being someone who loves automated documentation generation, manual representation has a broader semantic that should not be dismissed. There are probably a whole class of colours that ultimately might be requested - might be me - so I'd rather not blend these into color.pager.
Just my tuppence.
-Randall
next prev parent reply other threads:[~2021-05-17 22:55 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 [this message]
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
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='00b701d74b6f$aa295ed0$fe7c1c70$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=avarab@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).