All of lore.kernel.org
 help / color / mirror / Atom feed
From: "fkater@googlemail.com" <fkater@googlemail.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: trouble when ctrl/caps key swapped by X
Date: Fri, 21 Aug 2009 12:12:50 +0200	[thread overview]
Message-ID: <20090821101250.GE3549@comppasch2> (raw)
In-Reply-To: <4A8AB344.4080004@redhat.com>

Avi Kivity:

> On 08/17/2009 05:27 PM, fkater@googlemail.com wrote:
> > I have the ctrl/caps keys swapped by X in xorg.conf:
> >
> > Option "XkbOptions" "ctrl:swapcaps"
> >
> > The fact that this is not honoured by the guest (win2k)
> > might be intended or acceptable.
> >
> > However, when switching from the guest window to the host
> > and vice versa using the key combination Ctrl-Tab, the guest
> > additionally interprets that as a Caps Lock stroke. This is
> > of couse not intended.
> >
> > The result: After each Ctrl-Tab switch, win2k is alternates
> > between Caps Lock on an off...
> >
> > This does of course not happen when using a mouse click into
> > the guest window for switching to the guest.
>
> Does swapping the keys in the guest work?

Not really:

This is the result for keys pressed in a cmd.exe:

If Ctrl-f is pressed (Ctrl key is originally Caps Lock),
then you simply get an uppercase F (like when pressed
Shift-f).

If Caps Lock is pressed once (Caps Lock key is originally
Ctrl key), then all following keys are interpreted as
escaped letters (like when pressed with Ctrl normally):

* press Caps Lock once
* type f -> get ^F
* type g -> get ^G
* press Caps Lock once again to undo this behaviour

Note: There is also a registry hack under windows to swap
the Ctrl and Caps Lock keys which does makes things even
more confusing though.

Thank You
 Felix


WARNING: multiple messages have this Message-ID (diff)
From: "fkater@googlemail.com" <fkater@googlemail.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: trouble when ctrl/caps key swapped by X
Date: Fri, 21 Aug 2009 12:12:50 +0200	[thread overview]
Message-ID: <20090821101250.GE3549@comppasch2> (raw)
In-Reply-To: <4A8AB344.4080004@redhat.com>

Avi Kivity:

> On 08/17/2009 05:27 PM, fkater@googlemail.com wrote:
> > I have the ctrl/caps keys swapped by X in xorg.conf:
> >
> > Option "XkbOptions" "ctrl:swapcaps"
> >
> > The fact that this is not honoured by the guest (win2k)
> > might be intended or acceptable.
> >
> > However, when switching from the guest window to the host
> > and vice versa using the key combination Ctrl-Tab, the guest
> > additionally interprets that as a Caps Lock stroke. This is
> > of couse not intended.
> >
> > The result: After each Ctrl-Tab switch, win2k is alternates
> > between Caps Lock on an off...
> >
> > This does of course not happen when using a mouse click into
> > the guest window for switching to the guest.
>
> Does swapping the keys in the guest work?

Not really:

This is the result for keys pressed in a cmd.exe:

If Ctrl-f is pressed (Ctrl key is originally Caps Lock),
then you simply get an uppercase F (like when pressed
Shift-f).

If Caps Lock is pressed once (Caps Lock key is originally
Ctrl key), then all following keys are interpreted as
escaped letters (like when pressed with Ctrl normally):

* press Caps Lock once
* type f -> get ^F
* type g -> get ^G
* press Caps Lock once again to undo this behaviour

Note: There is also a registry hack under windows to swap
the Ctrl and Caps Lock keys which does makes things even
more confusing though.

Thank You
 Felix

  reply	other threads:[~2009-08-21 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 14:27 trouble when ctrl/caps key swapped by X fkater
2009-08-18 13:57 ` Avi Kivity
2009-08-18 13:57   ` [Qemu-devel] " Avi Kivity
2009-08-21 10:12   ` fkater [this message]
2009-08-21 10:12     ` fkater

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=20090821101250.GE3549@comppasch2 \
    --to=fkater@googlemail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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 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.