public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: linux-kbuild@vger.kernel.org, Roland Eggner <edvx1@systemanalysen.net>
Cc: Dmitry Voytik <dvv.kernel@gmail.com>,
	Michal Marek <mmarek@suse.cz>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] nconf:  function keys line, change background color for better readability
Date: Mon, 14 Jan 2013 23:20:12 +0100	[thread overview]
Message-ID: <201301142320.13141.yann.morin.1998@free.fr> (raw)
In-Reply-To: <20121229223328.GA28355@mobil.systemanalysen.net>

Roland, All,

On Saturday 29 December 2012 Roland Eggner wrote:
> >From: Roland Eggner <edvx1@systemanalysen.net>
> 
> •  In function keys line descriptions black on darkblue are almost impossible
>    to read.  Change colors to black on brown.
> 
> Signed-off-by: Roland Eggner <edvx1@systemanalysen.net>
> ---
> --- a/scripts/kconfig/nconf.gui.c	2012-11-16 17:47:22.000000000 +0100
> +++ b/scripts/kconfig/nconf.gui.c	2012-12-23 23:51:40.929833170 +0100
> @@ -48,7 +48,7 @@ static void set_normal_colors(void)
>  	init_pair(INPUT_FIELD, -1, -1);
>  
>  	init_pair(FUNCTION_HIGHLIGHT, -1, -1);
> -	init_pair(FUNCTION_TEXT, COLOR_BLUE, -1);
> +	init_pair(FUNCTION_TEXT, COLOR_YELLOW, -1);

Although I am not a fan of this color scheme, it is much more readable
than the previous black-on-blue. Tested in frame-buffer console, in konsole
and in xterm. And queued in my non-official for-next branch.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'


  reply	other threads:[~2013-01-14 22:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121228185108.GA13644@voyt-hp>
2012-12-28 19:40 ` [PATCH] nconf: add vi-style command keys for the menu navigation Dmitry Voytik
2012-12-29 22:33   ` [PATCH 2/2] nconf: function keys line, change background color for better readability Roland Eggner
2013-01-14 22:20     ` Yann E. MORIN [this message]
2013-01-14 22:26       ` Yann E. MORIN
2012-12-29 22:34   ` [PATCH 1/2] nconf: add keybindings for vi-style menu navigation, rewrite help texts Roland Eggner
2013-01-08 22:04     ` Yann E. MORIN
2013-01-14 18:24     ` Yann E. MORIN
2013-01-15 16:10       ` Roland Eggner
2013-01-15 16:26         ` [PATCH v2 " Roland Eggner
2013-01-15 16:36           ` [PATCH v2stable " Roland Eggner
2013-01-15 17:39             ` Yann E. MORIN
2013-01-15 22:27           ` [PATCH v2 " Yann E. MORIN
2013-01-16 20:19             ` Roland Eggner
2013-01-16 12:48           ` Michal Marek
2013-01-08 21:57   ` [PATCH] nconf: add vi-style command keys for the menu navigation Yann E. MORIN
2013-01-14 22:10   ` Yann E. MORIN
2013-01-15 17:12     ` Roland Eggner
2013-01-15 17:38       ` Yann E. MORIN
2013-01-15 17:55         ` Roland Eggner

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=201301142320.13141.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=dvv.kernel@gmail.com \
    --cc=edvx1@systemanalysen.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sboyd@codeaurora.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