From: Igor Djordjevic <igor.d.djordjevic@gmail.com> To: "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 21:48:17 +0200 [thread overview] Message-ID: <8811383b-d5f1-2b06-8ac7-47bbc5fc9d20@gmail.com> (raw) In-Reply-To: <60a7f7427eab6_55039208ba@natae.notmuch> Hi all, 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. And that's all there is to it. Software which is able to but does not show any colors by default does not need to care at all, as colors are an opt-in feature there already, so NO_COLOR serves no purpose. On the other hand, software which does enable (at least some) color by default, without user explicitly setting anything but requiring opt-out to disable color instead, should treat NO_COLOR precisely as that user requested opt-out, with an obvious convenience for the user being able to set NO_COLOR globally once and have all the programs supporting it recognize it as color opt-out exactly, without a need for the user to opt-out in each and every program separately (and differently). So, the whole point is make the default value be "no color" for each and every application consistently, where user (and _not_ developer) needs to opt-in in order to enable colors (in each and every application where colors are in fact still desired). Regards, Buga -- [1]: https://no-color.org/
next prev parent reply other threads:[~2021-05-21 19:48 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 [this message] 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 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=8811383b-d5f1-2b06-8ac7-47bbc5fc9d20@gmail.com \ --to=igor.d.djordjevic@gmail.com \ --cc=avarab@gmail.com \ --cc=felipe.contreras@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=leah@vuxu.org \ --cc=rsbecker@nexbridge.com \ --cc=sandals@crustytoothpaste.net \ --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).