All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <ken@linuxfromscratch.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Oleg Verych <olecom@flower.upol.cz>,
	Rene Herman <rene.herman@keyaccess.nl>, Willy Tarreau <w@1wt.eu>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Krzysztof Halasa <khc@pm.waw.pl>,
	Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>,
	Helge Deller <deller@gmx.de>
Subject: Re: syntax highlighting, emacs ([PATCH 0/2] Colored kernel output (run2))
Date: Mon, 8 Oct 2007 01:29:17 +0100	[thread overview]
Message-ID: <20071008002917.GB28926@deepthought> (raw)
In-Reply-To: <Pine.LNX.4.64.0710080005370.16301@fbirervta.pbzchgretzou.qr>

On Mon, Oct 08, 2007 at 12:11:21AM +0200, Jan Engelhardt wrote:
> 
> Actually, blue is perceived as one of the darkest colors by the human
> eye. There is a reason that the RGB -> grayscale transformation uses
> the following weighting: r=76 g=154 b=26.

 But, not every video card reproduces blue in the same way, let
alone every monitor - somewhere I've got an old CRT monitor where
blue text was mostly unreadable (_too_dark_).  For photo-editing,
I now use xgamma to get adequately-consistent results on whichever of
4 machines I'm using (one LCD monitor, with KVM switch) - the
settings for the individual machines are very different.

 And, of course, people have different colour vision (and unless we
are labelled as colour-blind, we each regard our colour vision as
"normal").  So, what is perfectly acceptable for you on specific
hardware may be totally unusable for someone else.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2007-10-08  1:00 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0710062005190.5969@fbirervta.pbzchgretzou.qr>
2007-10-06 19:13 ` [PATCH 1/2] Colored kernel output (run2) Jan Engelhardt
2007-10-08 13:28   ` Denys Vlasenko
2007-10-06 19:13 ` [PATCH 2/2] " Jan Engelhardt
     [not found] ` <20071006195105.GE22435@flower.upol.cz>
     [not found]   ` <20071006194820.GA30579@elte.hu>
2007-10-06 21:03     ` [PATCH 0/2] " Oleg Verych
2007-10-06 21:03       ` Jan Engelhardt
2007-10-06 21:55         ` About summary in the subject (Re: [PATCH 0/2] Colored kernel output (run2)) Oleg Verych
2007-10-07  6:07       ` [PATCH 0/2] Colored kernel output (run2) Ingo Molnar
2007-10-07 11:10         ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Oleg Verych
2007-10-07 14:15           ` NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)" Valdis.Kletnieks
2007-10-07 15:12             ` Alan Cox
2007-10-07 15:29               ` Jan Engelhardt
2007-10-07 16:23                 ` Alan Cox
2007-10-07 23:09                   ` Jan Engelhardt
2007-10-07 15:46               ` Valdis.Kletnieks
2007-10-07 18:11               ` NAK nettiquete (was " Arnaldo Carvalho de Melo
2007-10-07 16:12           ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Ingo Molnar
2007-10-07 18:47             ` Rene Herman
2007-10-07 18:58               ` Jan Engelhardt
2007-10-07 19:27                 ` Rene Herman
2007-10-07 20:02                   ` Jan Engelhardt
2007-10-07 19:13               ` Willy Tarreau
2007-10-07 19:47                 ` Oleg Verych
2007-10-07 21:23                   ` Ingo Molnar
2007-10-07 21:38                     ` Alan Cox
2007-10-12 13:42                       ` Bill Davidsen
2007-10-08  3:23                   ` Willy Tarreau
2007-10-08 19:27                     ` initramfs: coloring in userspace, "[PATCH 0/2] Colored kernel output (run2)" Oleg Verych
2007-10-07 19:53                 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Rene Herman
2007-10-07 19:56                 ` Jan Engelhardt
2007-10-07 20:00                   ` Rene Herman
2007-10-07 20:04                     ` Jan Engelhardt
2007-10-07 20:06                       ` Rene Herman
2007-10-07 20:50                       ` tty UI (Re: [PATCH 0/2] Colored kernel output (run2)) Oleg Verych
2007-10-07 20:43                         ` Jan Engelhardt
2007-10-07 22:18                           ` syntax highlighting, emacs ([PATCH " Oleg Verych
2007-10-07 22:11                             ` Jan Engelhardt
2007-10-08  0:29                               ` Ken Moffat [this message]
2007-10-08  3:29                   ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Willy Tarreau
2007-10-07 21:11                 ` Ingo Molnar
2007-10-07 23:02                   ` Oleg Verych
2007-10-07 23:01                     ` Jan Engelhardt
2007-10-07 23:33                       ` Oleg Verych
2007-10-07 22:40                 ` Alistair John Strachan
2007-10-07 23:10                   ` Rene Herman
2007-10-07 23:20                     ` Alistair John Strachan
2007-10-07 23:33                     ` Alistair John Strachan
2007-10-07 23:15                   ` Alan Cox
2007-10-07 16:37           ` Jan Engelhardt
2007-10-12 13:16           ` Bill Davidsen
2007-10-12 14:57             ` Oleg Verych

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=20071008002917.GB28926@deepthought \
    --to=ken@linuxfromscratch.org \
    --cc=Emilian.Medve@freescale.com \
    --cc=davej@redhat.com \
    --cc=deller@gmx.de \
    --cc=jengelh@computergmbh.de \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=olecom@flower.upol.cz \
    --cc=rene.herman@keyaccess.nl \
    --cc=w@1wt.eu \
    /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.