Re: (from comp.emacs.xemacs) Shift with KP-Add?

"Stephen J. Turnbull" <[email protected]>
Newsgroups gmane.emacs.xemacs.beta,gmane.comp.freedesktop.xorg,gmane.comp.xfree86.devel
Organization The XEmacs Project
Message-ID <[email protected]>
>>>>> "Aidan" == Aidan Kehoe <[email protected]> writes:

    Aidan> They (and I imagine x.org, until it’s proven otherwise)

X.org X11R6.8 allows binding all the function keys and keypad keys on
my PowerBook G4.

    Aidan> are shipping with keymaps that bind, for example,

    Aidan> keycode  63 = KP_Multiply XF86_ClearGrab

*goggle*

    Aidan> I’m sure there is some way to work around this within
    Aidan> XEmacs, and it’s probably going to be ugly and long,
    Aidan> because we various input methods, determined at compile
    Aidan> time, that may or may not use XLookupString. Whee.

It's worse than that, because the XFree86 behavior is known to be
incompatible with various commercial servers (specifically, Sun's).
Unless you special-case the servers according to vendor, there is no
right way to do it---the code that XFree86 developers recommended as a
workaround eats the Compose key (inter alia) on Sun.  Recent GTK+ has
some way to work around this, but it was not obvious how to apply to
XEmacs's event loop.

I think we should port our keyboard code to XKB where available (ISTR
this breakage requires XKB to have its intended effect in XFree86, so
this should cover all bases properly).



-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.