public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: splite-gentoo@sigint.cs.purdue.edu
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] more default DIR_COLORS
Date: Fri, 14 May 2004 10:28:07 -0500	[thread overview]
Message-ID: <20040514152807.GA16819@sigint.cs.purdue.edu> (raw)
In-Reply-To: <20040514095622.634dc1f1@beech.glades.net>

On Fri, May 14, 2004 at 09:56:22AM +0100, Daniel Armyr wrote:
> > and maybe others have suggestions for a sweeter DIR_COLORS ?
> 
> Just watch out for the dark blue (34) I got stuck with that before once on
> a black background and that was not fun in the long run.

Are there any published guidelines for developing colorized console apps?
Perhaps something like:

1.  If you change the foreground color, you must change the background
    to a contrasting color so the character is still visible.  (i.e.
    don't assume the default background color is constrasting)

2.  Remember that 10% of men (and some women too) are color-blind when
    chosing your colors.

3.  Consider using bold, underline, and/or reverse video instead.  (folks
    with dumb terminals for consoles will thank you)

4.  Only use color, reverse video, etc. when doing so conveys additional
    information to the user.  (i.e. don't make body text green just
    because you like green)

5.  Stick with plain text if you're not outputting to a tty.

6.  There is NO rule six.


I use black text on white background (you know, the default colors for
xterm, gnome-terminal, konsole, etc.) and still have trouble reading
the output from certain Gentoo-specific commands, most notably java-config.
portage -v output looks like fruit salad (light green package names on
a white background?  Why change the color of the package name at all?
I've never seen it be anything but green.)

Yes, I know about NOCOLOR and java-config -n.  I don't want to get rid
of the colors, I'd just like to see them used with a bit more care and
subtlety.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-14 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  4:21 [gentoo-dev] more default DIR_COLORS Mike Frysinger
2004-05-14  4:23 ` Andrew Gaffney
2004-05-14  4:35   ` Daniel Mills
2004-05-14  4:35   ` Mike Frysinger
2004-05-14  9:25     ` Stroller
2004-05-14  8:56 ` Daniel Armyr
2004-05-14 15:28   ` splite-gentoo [this message]
2004-05-15 11:34     ` Markus Nigbur
2004-05-14 20:52   ` Mike Frysinger
2004-05-15  8:14 ` Duane Healing

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=20040514152807.GA16819@sigint.cs.purdue.edu \
    --to=splite-gentoo@sigint.cs.purdue.edu \
    --cc=gentoo-dev@lists.gentoo.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