From: Denis Vlasenko <vda.linux@googlemail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: Re: [PATCH/RFC] kconfig/lxdialog: make lxdialof a built-in
Date: Sun, 30 Jul 2006 14:42:07 +0200 [thread overview]
Message-ID: <200607301442.07426.vda.linux@googlemail.com> (raw)
In-Reply-To: <20060728145947.GA29095@mars.ravnborg.org>
On Friday 28 July 2006 16:59, Sam Ravnborg wrote:
> > > The double ESC ESC thing I dunno how to fix.
> >
> > I think the easiest would be to just ignore the first ESC, it matches the
> > documented behaviour and e.g. mc has the same behaviour. The delay of the
> > single ESC makes it a bit annoying/confusing to use, so that sticking to
> > the double ESC is IMO safer.
> > I played with it a little and below is an example, which implements this
> > behaviour for the menu window.
>
> Thanks - will implment this for all the dialog_* functions.
I don't like "double ESC" idea at all.
I am a Midnight Commander user and I use "old ESC mode"
where single ESC works after a delay.
I patched mc to look at KEYBOARD_KEY_TIMEOUT_US environment variable
so that delay is configurable (instead of hardcoded 0.5 second one).
Will push the patch to mc-devel.
25 millisecond timeout works just fine on local ttys, serial lines,
and over ssh. So I am setting KEYBOARD_KEY_TIMEOUT_US=25000.
--
vda
next prev parent reply other threads:[~2006-07-30 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:27 [PATCH/RFC] kconfig/lxdialog: make lxdialof a built-in Sam Ravnborg
2006-07-28 14:09 ` Roman Zippel
2006-07-28 14:59 ` Sam Ravnborg
2006-07-30 12:42 ` Denis Vlasenko [this message]
2006-07-30 21:44 ` Sam Ravnborg
2006-07-30 22:19 ` Roman Zippel
2006-07-29 20:53 ` Sam Ravnborg
2006-07-29 20:56 ` Sam Ravnborg
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=200607301442.07426.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=sam@ravnborg.org \
--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