From: Karel Zak <kzak@redhat.com>
To: "Pádraig Brady" <P@draigbrady.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
kerolasa@gmail.com, "Dale R. Worley" <worley@alum.mit.edu>,
mrmazda@earthlink.net, util-linux <util-linux@vger.kernel.org>
Subject: Re: tty[1-6]: colors a negative accessibility/usability trend
Date: Mon, 2 Mar 2015 09:59:29 +0100 [thread overview]
Message-ID: <20150302085929.GG8046@ws.net.home> (raw)
In-Reply-To: <54F314D1.2080003@draigBrady.com>
On Sun, Mar 01, 2015 at 01:32:01PM +0000, Pádraig Brady wrote:
> On 27/02/15 13:48, Karel Zak wrote:
> > On Mon, Feb 16, 2015 at 11:32:41AM +0100, Samuel Thibault wrote:
> >> Karel Zak, le Mon 16 Feb 2015 10:47:47 +0100, a écrit :
> >>> On Mon, Feb 16, 2015 at 04:35:33AM -0500, Mike Frysinger wrote:
> >>>> On 16 Feb 2015 10:10, Karel Zak wrote:
> >>>>> What we want to duplicate? What exactly in lib/colors.c is duplicate?
> >>>>> The code evaluates filenames and parses files with "name colorcode".
> >>>>
> >>>> whether the terminal even supports color in the first place. if i picked a
> >>>> terminal that doesn't support color so i didn't have to worry about it, it's a
> >>>> bit crazy i also have to go to multiple config files and also tell them i don't
> >>>> want color otherwise i get corrupted output.
> >>>
> >>> For now it checks isatty() and nothing else, it would be possible to
> >>> check number of supported colors in terminfo too, or is there any
> >>> other way?
> >>
> >> It should also check how to change the colors. Not all terminals will
> >> support the ANSI way.
> >
> > OK, linked with libtinfo, now it checks if the current terminal supports
> > colors ("colors" from tinfo) and all the stuff is disabled for terminals
> > like vt100.
> >
> >>> Anyway, we don't want to create (duplicate) any database, all it
> >>> provides are knobs for customization and enable/disable.
> >>
> >> It provides only that because the source code currently hardcodes the
> >> \033[%sm sequence, but it really should not, and use terminfo instead.
> >
> > This is not implemented yet, I (or any volunteer?) will try to add to code
> > an extra layer to avoid the hardcoded sequences and read the colors from terminfo.
>
> I'd be careful to not over engineer that.
> coreutils currently hardcodes ansi sequences,
Yes, I know about it and coreutils has been my specimen for terminal-colors :-)
> and I've not heard specific complaints about it.
> What terminals are not catered for here?
I don't know, my plan is to do some research to better understand what
Samuel is talking about.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-03-02 8:59 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 [this message]
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
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=20150302085929.GG8046@ws.net.home \
--to=kzak@redhat.com \
--cc=P@draigbrady.com \
--cc=kerolasa@gmail.com \
--cc=mrmazda@earthlink.net \
--cc=samuel.thibault@ens-lyon.org \
--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