Problem with WinXP, XF86, Caps lock, xterm and cursor keys

[Harold L Hunt II]

The only special handling that I can think of is here:

<http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/\
hw/xwin/winkeybd.h?rev=1.3&content-type=text/x-cvsweb-markup>

Look at the section after the following line (WIN_NEW_KEYBOARD_SUPPORT 
is set to NO):

#else /* WIN_NEW_KEYBOARD_SUPPORT */

But that code just maps scan codes depending on whether or not the key 
is flagged as "extended", which sort of distinquishes the normal arrow 
keys from the keypad arrow keys, etc.

You see, we don't do this sort of translation on our own.  It may be 
that Windows is sending different codes when CapsLock is down, in which 
case we might want to translate those different codes to match the 
normal codes.  Does that make sense?

Harold

Alan Shutko wrote:

> Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de> writes:
> 
> 
>>Cygwin/XFree uses raw scancodes and uses XKB for symbol translation.
>>Your tweaking will most likely break this conversion.
> 
> 
> I could understand that, if it were consistent.  If Cygwin/XFree
> considered that key to still be caps lock, I could easily fix it with
> xmodmap.  But it doesn't, xev sees it as control.  Furthermore, why is
> it shifting arrow keys and page up/down but not anything else?
> 
> Finally, why is caps lock affecting those keys at all?  I haven't seen
> that on XFree86 on Linux, nor on any other X server I've tried.
> Personally, I suspect that some piece of code is handling things
> differently than the rest, so even the usual methods of fixing things
> (ie, xresources, xmodmap) may not fix things.  (But I'll be giving it
> a try, since it's easy.)
> 
> 
>>I declare such a modification as unsupported. You may still ask for
>>pointers to documentation 
> 
> 
> I'll take you up on that offer.  Could you point me to some
> info on how Cygwin/XFree86 gets those scancodes and runs the
> conversion?  Maybe I could put together a variant XKB layout without
> caps lock....
>