From: Karel Zak <kzak@redhat.com>
To: Felix Miata <mrmazda@earthlink.net>
Cc: util-linux@vger.kernel.org
Subject: Re: tty[1-6]: colors a negative accessibility/usability trend
Date: Thu, 12 Feb 2015 14:21:10 +0100 [thread overview]
Message-ID: <20150212132110.GE32318@ws.net.home> (raw)
In-Reply-To: <54DC762E.2090404@earthlink.net>
On Thu, Feb 12, 2015 at 04:45:18AM -0500, Felix Miata wrote:
> With util-linux >= 2.25 we can turn colors off via
>
> # touch /etc/terminal-colors.d/disable [3]
>
> for some commands, but far too few. It should apply to all, including many
> outside the purview of util-linux, and more importantly, do so by default.
This is never ending story and there is no setting which works for
everyone. All I want to provide tools to make it possible to support
various use-cases. It's downstream (distors) job to provide knobs to
switch between the use-cases (profiles).
For example I can imagine packages
fedora-terminal-colors-{high-contrast,disable,...}.rpm
to setup coreutils, util-linux, gcc, ... whatever.
> It should be up to those who wish a legibility reduction to discover how to
> and apply the reduction, not the other way around as it is now. It is much
> more difficult for those who cannot handle low contrast to improve it than
> for those who find it too high to reduce it, a variation on the chicken/egg
> paradigm.
We can also add --{disable,enable}-colors-by-default to move the
decision to downstream and use default according the current
terminal-colors.d setting. Your default will be disable, my enabled.
For example for fedora I will keep the colors enabled, because it's
current distribution policy.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-02-12 13:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 9:45 tty[1-6]: colors a negative accessibility/usability trend Felix Miata
2015-02-12 11:04 ` Pádraig Brady
2015-02-13 3:21 ` Dale R. Worley
2015-02-13 9:21 ` Karel Zak
2015-02-13 10:33 ` Sami Kerola
2015-02-13 11:25 ` Karel Zak
2015-02-15 11:12 ` Mike Frysinger
2015-02-16 9:10 ` Karel Zak
2015-02-16 9:35 ` Mike Frysinger
2015-02-16 9:47 ` Karel Zak
2015-02-16 10:32 ` Samuel Thibault
2015-02-16 13:49 ` Karel Zak
2015-02-27 13:48 ` Karel Zak
2015-03-01 13:32 ` Pádraig Brady
2015-03-01 15:14 ` Peter Cordes
2015-03-02 8:59 ` Karel Zak
2015-03-02 9:31 ` Samuel Thibault
2015-03-02 11:03 ` Karel Zak
2015-02-15 17:38 ` Dale R. Worley
2015-02-16 9:18 ` Karel Zak
2015-02-13 17:55 ` Bruce Dubbs
2015-02-12 13:21 ` Karel Zak [this message]
2015-02-12 13:56 ` Samuel Thibault
2015-02-12 14:38 ` Karel Zak
2015-02-12 15:25 ` Edward d'Auvergne
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=20150212132110.GE32318@ws.net.home \
--to=kzak@redhat.com \
--cc=mrmazda@earthlink.net \
--cc=util-linux@vger.kernel.org \
/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