mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nir Tzachar <nir.tzachar@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: nconfig v7
Date: Mon, 14 Dec 2009 07:39:23 +0200	[thread overview]
Message-ID: <9b2db90b0912132139m702db437x64a70a98c16667b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.0912131118280.28039@obet.zrqbmnf.qr>

>>10x ;)
>
> Ten times what?

Thanks...

>>> - provide the same color scheme as menuconfig
>>
>>As far as colrs are involved, I think it is best to not impose any
>>color scheme. You can never satisfy everyone, and will get into
>>endless fights about which is best.
>
> Well, menuconfig seems to have had the least fights. There was exactly
> one color scheme imposed, and that did not change for years; when themes
> were added, not much happened. There was a bit of discussion and
> submissions about themes (including myself), but in the end, it was
> sort-of agreed upon that four were enough. And they seem to work for
> everybody.
>
>>I believe the current approach in nconfig works best, as I am using
>>the default terminal colors for the main body of text (menus, help
>>text, etc), and only use colors for emphasis (headings, boxes, etc).
>
> No sorry. Black-on-blue does not work very much, for the physical fact
> that blue is recognized as faint. Let me put in some numbers (30,59,11%
> are the common RGB weighting for grayscale/luminance)
>
>  Blue:                       Effective Lum:
>  - xterm standard (#0000EE): 26.18
>  - VGA standard (#0000AA):   18.70
>  Cyan:
>  - VGA (#00AAAA)             119.00
>
> So you see why Midnight Commander, htop, etc. all use Black-on-Cyan for
> their Fn keybar instead of Blue.

I'll go along with you, but only as fat as the highlights are
concerned. I will oppose any kind of color theme for the main body of
text, as it will just lead to arguments about readability, etc., which
I feel no one would win but the loudest complainer. Again, I believe
it is best to make use as much as possible of the colors the user has
picked for her terminal, as she had already made the best choice for
_her_.

  parent reply	other threads:[~2009-12-14  5:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 19:55 Jan Engelhardt
2009-12-12 11:37 ` Michal Marek
2009-12-13  7:23 ` Nir Tzachar
2009-12-13 11:09   ` Jan Engelhardt
2009-12-13 11:55     ` Sam Ravnborg
2009-12-13 14:25       ` Jan Engelhardt
2009-12-13 17:28         ` Sam Ravnborg
2009-12-14  5:34           ` Nir Tzachar
2009-12-14  5:39     ` Nir Tzachar [this message]
2009-12-14  5:41     ` Nir Tzachar
2009-12-14 12:26       ` Jan Engelhardt
2009-12-14 13:45         ` Nir Tzachar
2009-12-14 13:51           ` Jan Engelhardt

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=9b2db90b0912132139m702db437x64a70a98c16667b@mail.gmail.com \
    --to=nir.tzachar@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®