From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Igor Djordjevic" <igor.d.djordjevic@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, "Randall S. Becker" <rsbecker@nexbridge.com>,
Leah Neukirchen <leah@vuxu.org>
Subject: Re: [PATCH] help: colorize man pages
Date: Fri, 21 May 2021 18:04:25 -0500 [thread overview]
Message-ID: <60a83c794ed4d_81cd4208f3@natae.notmuch> (raw)
In-Reply-To: <636007b7-c079-f8a6-1b26-eb2a55505354@gmail.com>
Igor Djordjevic wrote:
> On 21/05/2021 23:20, Felipe Contreras wrote:
> > Igor Djordjevic wrote:
> > >
> > > If I may, NO_COLOR approach seems to be rather straightforward to me,
> > > as per description on their homepage[1] - make all software supporting
> > > it behave as colors are an opt-in feature, thus disabled by default.
> >
> > May I ask you how you interpret this?
> >
> > It is reasonable to configure certain software such as a text editor
> > to use color ... sparingly
>
> Sure, but to make the point (hopefully) even more obvious, let me
> quote the whole part:
>
> It is reasonable to configure certain software such as a text editor
> to use color or other ANSI attributes sparingly (such as the reverse
> attribute for a status bar) while still desiring that other software
> not add color unless configured to. It should be up to the user
> whether color is used, not the software author.
>
> I understand it exactly as (I think) it says - it is reasonable to
> allow (the user, not developer!) to configure certain software to
> (still) use color
This does not follow.
The contraposition of that statement is that if a text editor doesn't
use color sparingly, then the user should not be allowed to configure
such software.
Do you really think that's what they are saying? The user should not
have a choice? (with certain software) That's color fascism.
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-21 23:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 1:01 [PATCH] help: colorize man pages 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 [this message]
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
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
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=60a83c794ed4d_81cd4208f3@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=igor.d.djordjevic@gmail.com \
--cc=leah@vuxu.org \
--cc=rsbecker@nexbridge.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.
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).