From: andrzej zaborowski <balrogg@gmail.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix curses return key when using -k
Date: Wed, 3 Mar 2010 00:16:12 +0100 [thread overview]
Message-ID: <fb249edb1003021516j50053421lc7a4ea271ccbb9@mail.gmail.com> (raw)
In-Reply-To: <20100228143519.GM11637@const.famille.thibault.fr>
On 28 February 2010 15:35, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> Hello,
>
> There is a small incoherency in curses_keys.h, which makes it fail to
> emit \n when using e.g. -k fr: curses2keysym transforms \r and 0x157
> into \n, but name2keysym binds \r with Return, not \n. The patch below
> fixes that.
Thanks, applied both patches.
Cheers
prev parent reply other threads:[~2010-03-02 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 14:35 [Qemu-devel] [PATCH] Fix curses return key when using -k Samuel Thibault
2010-02-28 17:06 ` [Qemu-devel] " Samuel Thibault
2010-03-02 23:16 ` andrzej zaborowski [this message]
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=fb249edb1003021516j50053421lc7a4ea271ccbb9@mail.gmail.com \
--to=balrogg@gmail.com \
--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).