linux-kernel - Re: [PATCH] ncurses based config V2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Nov 2008 03:33:46 +0100 (CET)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	Willy Tarreau <w@....eu>, linux-kernel@...r.kernel.org,
	bzolnier@...il.com, linux-kbuild@...r.kernel.org,
	ariveira@...il.com, rdunlap@...otime.net,
	kosaki.motohiro@...fujitsu.com, 7eggert@....de,
	Nir Tzachar <nir@...char.com>
Subject: Re: [PATCH] ncurses based config V2

Hi,

On Mon, 24 Nov 2008, Sam Ravnborg wrote:

> >   - colors are too dark.
> Seconded. Please try to find a lighter set of default colors.
> You may be inspired by one of the menuconfig color-sets.
> 
> I agree that we could use a lift here - so please do not go for the
> default color set of menuconfig.

Well, the current colors seems to usable on wide variety of terminals, but 
I'm not colorblind, so I can't really complain. :)
Before we keep discussing the colors, I'd rather suggest to drop them 
completely and maybe use colors for what actually needs attention.

> >   - I'm not convinced that the parenthesis around hotkeys make the menu
> >     that much readable, especially when there are lots of short words or
> >     even acronyms. Eg :
> >         [ ]   (U)TS namespace
> >         [ ]   (I)PC namespace
> >         [ ]   (U)ser namespace (EXPERIMENTAL)
> >         [ ]   (P)ID Namespaces (EXPERIMENTAL)
> 
> This looks like some ancient stuff and it must be a better way to
> show the short-cuts.

The parenthesis make it really annoying to read...

> I would really appreciate if you could look into the above issues.
> If you do a repost with this fixed I will try to do a proper review,
> including code-review next time.

The code is rather large, so it might be better to split the code into two 
sources, one for kconfig logic and the other for the interface logic, so 
it becomes easier to read and maintain.

bye, Roman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/