Ar an t-ochtú lá déag de mí na Samhain, scríobh Joachim Schrod:
> Bad explained sorry, what I meant is the following: I use my
.Xmodmap
> to map the print and the break key to F13 and F15, using
>
> keycode 0x6F = F13 Sys_Req
> keycode 0x6E = F15 Break
>
> If I do that I can bind `F13', control and meta `F13', but not
> shift `F13', so the situation seems different.
But that looks very similar. Did you try to leave off Sys_Req and Break
from your keycode definition? Does XEmacs detect Sh-F13 then?
Yeah, one would imagine that mapping would pass Sys_Req to XEmacs when
shift-F13 is pressed, but it doesn’t (with my installation, too). That said,
leaving off the second column does allow XEmacs to see shift-F13 here.
Somewhere the code has to decide if it shall associate a modifier or
not
(from a first glance, that might be the loop at the end of
x_reset_key_mapping() in event-Xt.c). And here something seems to go
wrong.
XEmacs isn’t doing anything wrong, it’s the libraries are broken.
Still. We need to include code to deal with XKB if that is available when we
build. That won’t address the problem if we build on a machine without XKB
available, and display on one with this insanity, but that’s a relative
corner case.
--
“I, alone, perhaps, in this city of nearly two million, view it with sadness,
sympathy, and respect, seeing in the millions of Russian youngsters who laid
down their lives in that war a tragedy rising above all the political
emotions of that time [...]” -- George Kennan on Vienna's „Erbsenkönig“