"Bernhard R. Link" <[email protected]> writes:
> That is normal, as ratpoison got the key, it has to fake a key-press
> and xterm is ignoring keys not directly from the X server by default.
> (try enabling "Allow SendEvent" in xterm, then it should get this key).
I realized that, a short while after filing the bugreport.
> I'm not able to reproduce this. Using a .ratpoisonrc like that seems
> to work fine here (well, section needs shift and onehalf needs altgr,
> so it is quite hard to use, but it works using 1.4.3-1)
[...]
> I'm out of ideas here.
>
> Only difference in my setting is that my X server is not lenny's but a
> remote one. But I hope that should not make any difference...
Any suggestions on how I can help debug it? I'm also very puzzled,
since the same commands work fine from the command line (ratpoison -c
'...'). For example, is there any easy (besides looking at the i/o
with strace) to log the communication between ratpoison and the
X-server?
My X-server, according to xdpyinfo:
name of display: :0.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 10402000
X.Org version: 1.4.2
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
[...]
I'm not very familar with xorg or debian's packaging thereof, but the
packages I have installed are:
$ dpkg -l 'xserver*' |grep '^ii'
ii xserver-xfree86 1:7.1.0-19
transitional package for moving from XFree86
ii xserver-xorg 1:7.3+18 the
X.Org X server
ii xserver-xorg-core 2:1.4.2-10 Xorg
X server - core server
ii xserver-xorg-input-all 1:7.3+18 the
X.Org X server -- input driver metapacka
ii xserver-xorg-input-evdev 1:2.0.8-1
X.Org X server -- evdev input driver
ii xserver-xorg-input-kbd 1:1.3.1-1
X.Org X server -- keyboard input driver
ii xserver-xorg-input-mouse 1:1.3.0-1
X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics 0.14.7~git20070706-3
Synaptics TouchPad driver for X.Org/XFree86
ii xserver-xorg-input-wacom 0.7.9.3-2
X.Org X server -- Wacom input driver
ii xserver-xorg-video-via 1:0.2.2-6
X.Org X server -- VIA display driver
ii xserver-xorg-video-voodoo 1:1.2.0-1
X.Org X server -- Voodoo display driver
I'm using the VIA driver, and it seems I have kbd enabled.
>From xev, I get the following events when I press and release the §
key, then repeat it while also pressing shift. This is with C-t as the
escape character (with § as the escape character, I naturally don't
see those keypresses with xev).
KeyPress event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243070803, (424,896), root:(425,897),
state 0x0, keycode 49 (keysym 0xa7, section), same_screen YES,
XLookupString gives 1 bytes: (a7) "§"
XmbLookupString gives 1 bytes: (a7) "§"
XFilterEvent returns: False
KeyRelease event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243070928, (424,896), root:(425,897),
state 0x0, keycode 49 (keysym 0xa7, section), same_screen YES,
XLookupString gives 1 bytes: (a7) "§"
XFilterEvent returns: False
KeyPress event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243072176, (424,896), root:(425,897),
state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243072576, (424,896), root:(425,897),
state 0x1, keycode 49 (keysym 0xbd, onehalf), same_screen YES,
XLookupString gives 1 bytes: (bd) "½"
XmbLookupString gives 1 bytes: (bd) "½"
XFilterEvent returns: False
KeyRelease event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243072663, (424,896), root:(425,897),
state 0x1, keycode 49 (keysym 0xbd, onehalf), same_screen YES,
XLookupString gives 1 bytes: (bd) "½"
XFilterEvent returns: False
KeyRelease event, serial 27, synthetic NO, window 0x1600001,
root 0x49, subw 0x0, time 243073064, (424,896), root:(425,897),
state 0x1, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
which looks sane, as far as I can tell.
Regards,
/Niels
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
