From: worley@alum.mit.edu (Dale R. Worley)
To: kerolasa@gmail.com
Cc: kzak@redhat.com, P@draigbrady.com, mrmazda@earthlink.net,
util-linux@vger.kernel.org
Subject: Re: tty[1-6]: colors a negative accessibility/usability trend
Date: Sun, 15 Feb 2015 12:38:32 -0500 [thread overview]
Message-ID: <87h9unt6qv.fsf@hobgoblin.ariadne.com> (raw)
In-Reply-To: <CAG27Bk0JrVSbKEBqeEr63O4cz3B5zyDmGw_MFVzXYTbWjZ2URQ@mail.gmail.com> (kerolasa@iki.fi)
Sami Kerola <kerolasa@iki.fi> writes:
> Or add the needed to ncurses. Isn't that better than adding a new
> library?
That would work, but only for utilities that use ncurses. OTOH, it
would be good if ncurses understood and provided information from the
general color configuration to programs that use it.
Bruce Dubbs <bruce.dubbs@gmail.com> writes:
> Why not use the LS_COLORS environment variable used by coreutils' dircolors?
> Does util-linux need to create something different?
Using an environment variable is the standard Unix way of configuring
the user-oriented behavior of programs. But the "definition" of
LS_COLORS seems to be very specific to "ls".
The /etc/terminal-colors.d system seems a bit oversized (all those
files!), but it seems unlikely that anything simpler would work for a
large set of utilities, each of which the user may want to customize.
The main deficiency of terminal-colors.d is that it's system-wide. But
I see this in a blog:
$HOME/.config/terminal-colors.d overrides the global setting
so that is taken care of.
You also want to define an environment variable to override *that*,
e.g., files in $UTIL_LINUX_TERMINAL_COLORS override the ones in
$HOME/.config/terminal-colors.d -- that allows you to set up custom
environments for particular trees of processes by creating a suitable
colors directory and setting UTIL_LINUX_TERMINAL_COLORS.
Dale
next prev parent reply other threads:[~2015-02-15 17:46 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 [this message]
2015-02-16 9:18 ` Karel Zak
2015-02-13 17:55 ` Bruce Dubbs
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=87h9unt6qv.fsf@hobgoblin.ariadne.com \
--to=worley@alum.mit.edu \
--cc=P@draigbrady.com \
--cc=kerolasa@gmail.com \
--cc=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