From: Willy Tarreau <w@1wt.eu>
To: Nir Tzachar <nir@tzachar.com>
Cc: Nir Tzachar <tzachar@grad120a.cs.bgu.ac.il>,
linux-kernel@vger.kernel.org, bzolnier@gmail.com,
zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
ariveira@gmail.com, rdunlap@xenotime.net,
kosaki.motohiro@jp.fujitsu.com, 7eggert@gmx.de
Subject: Re: [PATCH] ncurses based config V2
Date: Sun, 14 Sep 2008 12:52:50 +0200 [thread overview]
Message-ID: <20080914105250.GB3811@1wt.eu> (raw)
In-Reply-To: <9b2db90b0809052241m39667ae6x14270ff942beeff@mail.gmail.com>
Hello,
sorry, it seems I missed this mail.
On Sat, Sep 06, 2008 at 08:41:56AM +0300, Nir Tzachar wrote:
> Hello.
>
> On Fri, Sep 5, 2008 at 10:59 PM, Willy Tarreau <w@1wt.eu> wrote:
> > Hello,
> >
> > On Fri, Sep 05, 2008 at 11:27:00AM +0300, Nir Tzachar wrote:
> >> Changes:
> >> 1) Fixed segfaults in help window.
> >> 2) Removed the instructions window, made the instructions appear as a button
> >> which displays a popup window.
> >> 3) Added hot keys support. As ncurses does not support several colors inside
> >> a menu, keys are highlighted using "()".
> >> 4) Optimized for 80x24 terminals.
> >> 6) Fixed zconf.y to use _menu_init
> >> 7) added nconfig to "make help"
> >> 8) Misc fixes.
> >>
> >> Comments are appreciated.
> >
> > OK, I've just tried it. Here are the first comments I can make :
> >
> > - colors are too dark. Cyan on black is barely readable, red on black is
> > almost unreadable and blue on black is not readable at all, I have to
> > switch off the light to read it. Most often you'll see light shades of
> > grey (even white) in interfaces because it's hard to see dark shades,
> > and bright flashy letters would dazzle and be seen as fuzzy. Many colors
> > are perfectly readable on while or even light grey (except yellow and
> > sometimes cyan). Blue backgrounds were often used under DOS and were
> > OK with almost all colors except red (well-known eye focus problem).
> > But there was a trick, pixels were very large in 640x200, nowaydays
> > we have small pixels and letters are not much readable anymore on blue
> > backgrounds. For your tests, you can try to load
> > xterm -bg <color> -fg <color> and ensure that you're using a medium
> > font (tickness of 1-pixel).
>
> The thing with colors is that they are very personal...
"personal" is true when it comes from a matter of taste. Here it's a matter
of readability.
> The colors I
> have work great on my terminals. I don't think I can come up with one
> scheme which looks nice to everybody, hence the support for color
> schemes.
I understand. I think that the original colors of make menuconfig are
OK and readable everywhere.
> If you can come up with a color scheme which works gr8 for
> you, I'll be happy to add it. If you are interested, check the
> INIT_PAIR macros of the patch.
OK I might do (I just don't have time right now).
> > - pressing arrows too fast regularly escapes (probably because of the
> > ESC prefix, I don't know). This is rather strange, because no other
> > application does this to me.
>
> I cannot reproduce this. What terminal emulator are you using, and
> which ncurses version?
I've just checked, ncurses-5.3. I also ensured that it's the same I
use with all my other progs (including mutt, vim, emacs, alsamixer,
less, gnuplot, kismet, lynx, ...). It is possible that there is something
very subtle, but I can't imagine what :-/
> Also, can you please send me the terminal emulator config file?
It's just a bare xterm running with TERM=xterm-color. I forgot to test on
the console.
> > Is there a specific initialization
> > sequence with ncurses to state that arrows should return special codes
> > instead of the ESC prefix ? (I have no idea)
>
> Yes. You need to specify you want to get keypad events, otherwise they
> just appear as ESC.
OK. I just found there is the ESCDELAY variable to define the ESC timeout.
They also talk about notimeout() in curs_inopts(3), which sounds pretty
well related to what I observe.
[skipping all fixed reports]
> > - 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)
>
> I agree, but could not come up with any other visible mark to note the hotkey.
>
> > I don't know if there is something such as a bold attribute in ncurses,
> > it would make sense to use it IMHO because you don't force a color on
> > people's terms, you rely on the style which works well for them.
>
> There is a bold attribute, but you cannot set it for a single letter
> of a menu item, as far as I know.
OK I understand. You might want to use the brighter color set (as menuconfig
does). Terminals sometimes translate them to bold characters.
> > I'm sorry I don't go further for now, the arrows causing frequent exits is
> > too bothersome, I've started it about 30 times just for this report, it's
> > too hard to navigate. I hope that the points above are already helpful.
>
> Thanks for the input. I would really like to solve the issue you have
> with arrow keys. Can you also send a trace of key presses which cause
> you to exit, and which window is active?
Sorry, the directory in which I built has been removed since. But it happened
in any window, starting with the main menu. That's why I think it's just an
initialization issue.
Regards,
Willy
next prev parent reply other threads:[~2008-09-14 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 19:11 [PATCH] ncurses based config Nir Tzachar
2008-09-03 19:38 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:02 ` Randy.Dunlap
2008-09-03 20:03 ` Randy.Dunlap
2008-09-03 20:18 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:29 ` Alejandro Riveira Fernández
2008-09-04 15:02 ` Bartlomiej Zolnierkiewicz
[not found] ` <9b2db90b0809032155h6ed5df9ey846de96779022d11@mail.gmail.com>
2008-09-04 15:28 ` Randy.Dunlap
2008-09-04 4:22 ` KOSAKI Motohiro
2008-09-04 10:36 ` Alejandro Riveira Fernández
2008-09-05 8:27 ` [PATCH] ncurses based config V2 Nir Tzachar
2008-09-05 13:49 ` Alejandro Riveira Fernández
2008-09-05 19:59 ` Willy Tarreau
2008-09-06 5:41 ` Nir Tzachar
2008-09-14 10:52 ` Willy Tarreau [this message]
2008-09-17 11:58 ` Nir Tzachar
2008-11-24 18:44 ` Sam Ravnborg
2008-11-25 2:33 ` Roman Zippel
2008-11-25 8:04 ` Nir Tzachar
2008-11-25 16:02 ` Roman Zippel
2008-11-25 8:01 ` Nir Tzachar
2008-11-25 8:11 ` Sam Ravnborg
2008-11-25 12:35 ` Nir Tzachar
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=20080914105250.GB3811@1wt.eu \
--to=w@1wt.eu \
--cc=7eggert@gmx.de \
--cc=ariveira@gmail.com \
--cc=bzolnier@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@tzachar.com \
--cc=rdunlap@xenotime.net \
--cc=tzachar@grad120a.cs.bgu.ac.il \
--cc=zippel@linux-m68k.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