This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Problem with WinXP, XF86, Caps lock, xterm and cursor keys
- From: Takuma Murakami <murakami at ipl dot t dot u-tokyo dot ac dot jp>
- To: cygwin-xfree at cygwin dot com
- Date: Wed, 26 Nov 2003 13:20:59 +0900
- Subject: Re: Problem with WinXP, XF86, Caps lock, xterm and cursor keys
- References: <874qwtilv2.fsf@wesley.springies.com>
- Reply-to: cygwin-xfree at cygwin dot com
Alan Shutko wrote:
> I've disabled my capslock key and turned it into a control key with
> this registry hack:
For your information, I am using the same scancode map
on a system. The system is JP Windows, US keyboard,
XKB enabled, no XF86Config file, and "setxkbmap -print"
prints:
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc/pc(pc101)+pc/us" };
xkb_geometry { include "pc(pc101)" };
};
I can't reproduce your problems on this system.
Ideally speaking, changes of Windows scancode mapper are
invisible from Cygwin/X. Because scancodes are the only
information Cygwin/X uses, your Caps Lock key and Control
key should be completely equivalent for Cygwin/X.
I hope you track down your problem.
Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp)