From: Jeff King <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: "brian m. carlson" <email@example.com>, Felipe Contreras <firstname.lastname@example.org>, email@example.com, Junio C Hamano <firstname.lastname@example.org>, "Randall S. Becker" <email@example.com> Subject: Re: [PATCH] help: colorize man pages Date: Wed, 19 May 2021 06:10:42 -0400 [thread overview] Message-ID: <YKTkIgdJgBomzieH@coredump.intra.peff.net> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, May 19, 2021 at 11:26:12AM +0200, Ævar Arnfjörð Bjarmason wrote: > > There's a big difference between Git coloring a Git UI, like a diff, and > > Git coloring a separate program that already has sensible, standard > > defaults. A user who has not configured any color settings would > > probably not want Git to render manual pages one way, cargo to render > > manual pages a second way, and still other programs to render manual > > pages in other, incompatible ways. We need to consider not only the > > impact that our decisions have in a vacuum, but what results similar > > decisions from other projects would produce in the software ecosystem as > > a whole. > > > > Would you consider various projects coloring their respective manual > > pages differently to be a desirable state of affairs? > > I think it's an important distinction that we're not coloring any manual > pages, it's a question of whether we invoke "man" invoked by "git help > <whatever>" with the exact same paramaters/options a user would get with > "man git-<whatever>". > > Right now our documentation seems to suggest that we won't do any such > magic, but you can also set man.viewer to e.g. invoke a web browser or > something instead of man(1). > > I don't think it's confusing in that context if we learn to do some "man > with fancy on top" in this mode. I agree that we could explain it as "man with fancy on top". But it makes me wonder: why is this Git's responsibility to do the fancy at all? I.e., if you want colorized manpages, why don't you configure man to do so? Sure, it's a bit of a pain to do so since it involves setting a bunch of obscure environment variables. But if that's what you want, wouldn't you want it for all manpages, whether you ran "git help log" or "man git-log" or "man ls"? This seems like a "man" feature and not a "git" feature. And arguably some of it is really a "less" feature (it is trying to set "standout" mode for its prompt, so configuring "so" and "se" termcap entries is just reinterpreting that. If you like, wouldn't you want it on for all "less" invocations?). -Peff
next prev parent reply other threads:[~2021-05-19 10:10 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 1:01 Felipe Contreras 2021-05-18 1:19 ` brian m. carlson 2021-05-18 3:22 ` Felipe Contreras 2021-05-18 23:49 ` brian m. carlson 2021-05-19 1:08 ` Junio C Hamano 2021-05-19 2:07 ` brian m. carlson 2021-05-19 6:09 ` Junio C Hamano 2021-05-19 8:41 ` Ævar Arnfjörð Bjarmason 2021-05-19 10:36 ` Felipe Contreras 2021-05-21 0:58 ` brian m. carlson 2021-05-21 18:09 ` Felipe Contreras 2021-05-21 19:48 ` Igor Djordjevic 2021-05-21 21:20 ` Felipe Contreras 2021-05-21 22:10 ` Igor Djordjevic 2021-05-21 23:04 ` Felipe Contreras 2021-05-22 18:38 ` Igor Djordjevic 2021-05-22 21:48 ` Felipe Contreras 2021-05-23 11:25 ` Igor Djordjevic 2021-05-23 14:48 ` Felipe Contreras 2021-05-21 22:47 ` Igor Djordjevic 2021-05-21 23:32 ` Junio C Hamano 2021-05-19 9:26 ` Ævar Arnfjörð Bjarmason 2021-05-19 10:10 ` Jeff King [this message] 2021-05-19 11:45 ` Felipe Contreras 2021-05-19 11:19 ` Felipe Contreras 2021-05-19 12:21 ` Felipe Contreras 2021-05-20 1:55 ` brian m. carlson 2021-05-20 2:23 ` Junio C Hamano 2021-05-20 3:05 ` Felipe Contreras 2021-05-20 3:28 ` Junio C Hamano 2021-05-20 3:48 ` Felipe Contreras 2021-05-20 2:45 ` Felipe Contreras 2021-05-19 10:25 ` 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=YKTkIgdJgBomzieH@coredump.intra.peff.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] help: colorize man pages' \ /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
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).