GNU bug report logs - #33398
26.1, netbsd-8; Hi Lock Faces, Hi Green B, default setting suggestion

Previous Next

Full log

Message #23 received at 33398 <at> debbugs.gnu.org (full text, mbox):

From: Van L <van <at> scratch.space>
To: Juri Linkov <juri <at> linkov.net>
Cc: 33398 <at> debbugs.gnu.org
Subject: Re: bug#33398: 26.1, netbsd-8;
 Hi Lock Faces, Hi Green B, default setting suggestion
Date: Tue, 20 Nov 2018 15:00:27 +1100

>>> Yes, the current shade of red is too glaring.
>> 
>> #ee2d3d is less glaring.
> 
> I see that the closest color for this is named "brown2".
> It's not required to always use colors with names,
> but in this case "brown2" is very close.  Another close
> candidates are "red2" and "firebrick2”.

Red2 (#ee0000) might be invisible to red-color blindness.
It could be too glaring still depending on taste.

The name firebrick2 hints closer to a kind of red than brown2.

> Then for hi-green we could use "green3”.

The 'light green' is easier on the eye, it seems to my eye
not having exclusively one color component in the RGB is better.

> Regarding your idea of using rainbow colors, the problem
> is that on TTY there are only these colors:
> 
> red, green, yellow, blue, magenta, cyan
> 
> hi-blue face uses cyan color, not blue, and
> hi-pink face uses magenta color, not red.
> 
> Since hi-yellow uses yellow, and hi-green uses green already,
> unfortunately there are no other colors available on TTY.

That’s a rabbit hole beyond scope. I am afraid.

If only the `Hi Green B' and `Hi Red B' are adjusted, or only the `Hi Green B’ is 
that improves the existing defaultsetting.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.