All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: "Dale R. Worley" <worley@alum.mit.edu>,
	"Pádraig Brady" <P@draigbrady.com>,
	mrmazda@earthlink.net, util-linux <util-linux@vger.kernel.org>
Subject: Re: tty[1-6]: colors a negative accessibility/usability trend
Date: Fri, 13 Feb 2015 12:25:23 +0100	[thread overview]
Message-ID: <20150213112523.GP32318@ws.net.home> (raw)
In-Reply-To: <CAG27Bk0JrVSbKEBqeEr63O4cz3B5zyDmGw_MFVzXYTbWjZ2URQ@mail.gmail.com>

On Fri, Feb 13, 2015 at 10:33:23AM +0000, Sami Kerola wrote:
> On 13 February 2015 at 09:21, Karel Zak <kzak@redhat.com> 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/... :-)
> 
> Or add the needed to ncurses. Isn't that better than adding a new
> library?

you want to link programs like dmesg, gcc or ls with ncurses monster?

The another story is that ncurses provides completely abstract layer
for colors and I didn't found a way how to use it together with color 
escape sequences. This is reason why for example cfdisk supports only
enable/disable terminal-colors.d feature, but no schemes to specify
colors.
    
    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2015-02-13 11:25 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 [this message]
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
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=20150213112523.GP32318@ws.net.home \
    --to=kzak@redhat.com \
    --cc=P@draigbrady.com \
    --cc=kerolasa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.