From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff King" <peff@peff.net>
Subject: How dow we educate our users to configure less?
Date: Tue, 08 Jun 2021 12:49:52 -0500 [thread overview]
Message-ID: <60bfadc0aca09_1abb8f208fd@natae.notmuch> (raw)
It has been suggested that we "educate our users" to configure less in
the right way, instead of colorizing man pages ourselves [1].
The question is *how*? Nobody has answered that.
This is a continuation of the thread below.
Felipe Contreras wrote:
> Jeff King wrote:
> > Moreover, I think that if they like colorized manpages, they'd probably
> > want them when running "man" themselves.
>
> This doesn't matter.
>
> The user might have "configured" man like this:
>
> man() {
> LESS_TERMCAP_md=$'\e[01;31m' \
> LESS_TERMCAP_me=$'\e[0m' \
> LESS_TERMCAP_so=$'\e[01;44;33m' \
> LESS_TERMCAP_se=$'\e[0m' \
> LESS_TERMCAP_us=$'\e[01;32m' \
> LESS_TERMCAP_ue=$'\e[0m' \
> command man "$@"
> }
>
> Git isn't going utilize that.
>
> Arch Linux recommends the above, and so does many online resources.
>
> So even if it's the case what you said, that they want colorized man
> pages, *and* they have man configured, that doesn't matter.
>
> In addition, not everyone is a Linux guru. Some might want colorized man
> pages, but not know how to get them.
>
> I myself only learned it was possible to configure that about a year ago
> when reading Arch Linux's installation guide. Luckily I clicked "Color
> output in console", even though I thought I already had most console
> software configured.
>
> I have 20 years of experience using Linux. Some people have less.
>
> You presume too much of our users.
>
> And you still haven't explained how they can properly configure
> colorized man pages for both man and git, in a way that works in all
> distributions.
>
> [1] https://wiki.archlinux.org/title/Color_output_in_console
I am still waiting for an explanation.
How does the user properly colorize man pages for both man and git in a
way that works in all distributions?
Cheers.
[1] https://lore.kernel.org/git/20210523054454.1188757-1-felipe.contreras@gmail.com/
--
Felipe Contreras
next reply other threads:[~2021-06-08 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 17:49 Felipe Contreras [this message]
2021-06-28 18:11 ` How dow we educate our users to configure less? Felipe Contreras
2021-06-28 18:46 ` Randall S. Becker
2021-06-28 19:01 ` Felipe Contreras
2021-06-28 19:34 ` Randall S. Becker
2021-06-28 19:44 ` Felipe Contreras
2021-06-28 19:58 ` Randall S. Becker
2021-06-28 20:17 ` Felipe Contreras
2021-06-28 20:37 ` Randall S. Becker
2021-06-28 20:51 ` Felipe Contreras
2021-06-28 20:56 ` Randall S. Becker
2021-06-28 21:09 ` 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=60bfadc0aca09_1abb8f208fd@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).