All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, shaharh@gmail.com, qemu-devel@nongnu.org,
	Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] Re: Qemu does not pass pressed caps lock to client
Date: Fri, 12 Feb 2010 09:15:11 -0600	[thread overview]
Message-ID: <4B75707F.7040105@codemonkey.ws> (raw)
In-Reply-To: <4B754C04.4080907@redhat.com>

On 02/12/2010 06:39 AM, Paolo Bonzini wrote:
>     /* There are two versions around of a Debian patch that changes the
>        way Caps Lock and Num Lock are handled.  The first version
>        by default sends only one of the KeyDown/KeyUp events, unless
>        SDL_DISABLE_LOCK_KEYS is present in the environment.  The second
>        version instead by default sends both events, unless
>        SDL_DISABLE_LOCK_KEYS is present and not empty.  This version
>        is the most commonly found (and a totally braindead idea).
>
>        Upstream instead supports SDL_NO_LOCK_KEYS which, if set to 1,
>        will generate all four events---which is what we want.  Luckily,
>        there is a combination of environment variable that will satisfy
>        all variant.  */
>
>     putenv ("SDL_DISABLE_LOCK_KEYS", "");
>     putenv ("SDL_NO_LOCK_KEYS", "1");
>
> Yes, I love Debian.

So basically, Debian carries a hacked version of SDL that changes the 
key press behaviour?

That's a Debian/Ubuntu bug.  Shame on them for changing the behaviour of 
a library API like that.

Regards,

Anthony Liguori

> Paolo
>
>

  reply	other threads:[~2010-02-12 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 21:13 [Qemu-devel] Qemu does not pass pressed caps lock to client Shahar Havivi
2010-02-12  9:54 ` Kevin Wolf
2010-02-12 11:09   ` Shahar Havivi
2010-02-12 11:43     ` Kevin Wolf
2010-02-12 12:39     ` [Qemu-devel] " Paolo Bonzini
2010-02-12 15:15       ` Anthony Liguori [this message]
2010-02-12 18:17         ` Paolo Bonzini
2010-02-12 18:44           ` Anthony Liguori
2010-02-12 20:49             ` Dustin Kirkland
2010-02-13 11:21               ` Paolo Bonzini

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=4B75707F.7040105@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kirkland@canonical.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shaharh@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.