qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Fix curses interaction with keymaps
Date: Sun, 28 Feb 2010 21:13:44 +0100	[thread overview]
Message-ID: <20100228201344.GE11637@const.famille.thibault.fr> (raw)
In-Reply-To: <20100228200300.GD11637@const.famille.thibault.fr>

Samuel Thibault, le Sun 28 Feb 2010 21:03:00 +0100, a écrit :
> The combination of keymap support (-k option) and curses is currently
> very broken.  The patch below fixes it by first extending keymap support
> to interpret the shift, ctrl, altgr and addupper keywords in keymaps,
> and to fix curses into properly using keymaps.

(to be applied on top of the two others)

Samuel

  reply	other threads:[~2010-02-28 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 20:03 [Qemu-devel] [PATCH] Fix curses interaction with keymaps Samuel Thibault
2010-02-28 20:13 ` Samuel Thibault [this message]
2010-03-06 22:20 ` Aurelien Jarno
2010-03-28 18:39 ` [Qemu-devel] [PATCH] baum: add destroy hook Samuel Thibault
2010-04-08 19:17   ` Aurelien Jarno

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=20100228201344.GE11637@const.famille.thibault.fr \
    --to=samuel.thibault@gnu.org \
    --cc=qemu-devel@nongnu.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).