From: Gerd Hoffmann <kraxel@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Reduce curses escdelay from 1s to 0.2s
Date: Wed, 26 Oct 2016 14:51:00 +0200 [thread overview]
Message-ID: <1477486260.18984.54.camel@redhat.com> (raw)
In-Reply-To: <20161015172439.GA16269@var>
On Sa, 2016-10-15 at 19:24 +0200, Samuel Thibault wrote:
> Hello,
>
> Peter Maydell, on Wed 22 Jun 2016 21:49:04 +0100, wrote:
> > On 22 June 2016 at 16:44, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> > > By default, curses will only report single ESC key event after 1s delay,
> > > since ESC is also used for keypad escape sequences. This however makes users
> > > believe that ESC is not working. Reducing to 0.2s provides good enough user
> > > experience, while still allowing 200ms for keypad sequences to get in, which
> > > should be more than enough.
> >
> > That the default delay is this massive seems like a bug in curses,
> > but I don't suppose it's likely to be changed at this point :-(
>
> So, could this be applied? Otherwise e.g. DOS applications ESC actions
> are very slugguish and thus look bogus in the ncurses UI.
Somehow slipped through and not in my qemu-devel folder any more.
Can you resend?
thanks,
Gerd
next prev parent reply other threads:[~2016-10-26 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:44 [Qemu-devel] [PATCH] Reduce curses escdelay from 1s to 0.2s Samuel Thibault
2016-06-22 20:49 ` Peter Maydell
2016-06-22 21:06 ` Samuel Thibault
2016-06-22 21:11 ` Peter Maydell
2016-10-15 17:24 ` Samuel Thibault
2016-10-26 12:51 ` Gerd Hoffmann [this message]
2016-10-26 15:20 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2016-10-30 11:38 Samuel Thibault
2019-03-03 6:14 Samuel Thibault
2019-03-03 17:11 ` Warner Losh
2019-03-03 17:26 ` Samuel Thibault
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=1477486260.18984.54.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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;
as well as URLs for NNTP newsgroup(s).