From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>, "Dale R. Worley" <worley@alum.mit.edu>
Cc: "Pádraig Brady" <P@draigBrady.com>,
mrmazda@earthlink.net, util-linux@vger.kernel.org
Subject: Re: tty[1-6]: colors a negative accessibility/usability trend
Date: Fri, 13 Feb 2015 11:55:58 -0600 [thread overview]
Message-ID: <54DE3AAE.2010906@gmail.com> (raw)
In-Reply-To: <20150213092131.GM32318@ws.net.home>
Karel Zak wrote:
> On Thu, Feb 12, 2015 at 10:21:48PM -0500, Dale R. Worley wrote:
>> I don't particularly like colorization. But technically, it seems to me
>> that what is needed is a systematic way for the user to indicate his
>> colorization preferences to *all* utilities. And a corresponding way
>> for the system to provide defaults for those user preferences.
>>
>>
>> Only when there is a systematic framework for colorization will all the
>> programs allow colorizing to be configured.
>
> It would be possible to create a shared library from our lib/colors.c
> to support terminal-colors.d/... :-)
Why not use the LS_COLORS environment variable used by coreutils' dircolors?
Does util-linux need to create something different?
-- Bruce
next prev parent reply other threads:[~2015-02-13 17:55 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 [this message]
2015-02-12 13:21 ` Karel Zak
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=54DE3AAE.2010906@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=P@draigBrady.com \
--cc=kzak@redhat.com \
--cc=mrmazda@earthlink.net \
--cc=util-linux@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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