I have removed this x-compose.el file and converted all my xmodmaps to
use the dead_acute keysym.
As far as Linux and SGI are concerned, ignoring these vendor-specific
keysyms seems appropriate. If I had access to a 0.7.0 binary for
IRIX, I could provide further evidence.
Thanks for your efforts.
Gisli
>>>>> On Fri, 28 May 1999 11:54:13 -0500, you said:
JH> fixed crash on X11 due to vendor-specific (>0xffff) keysyms.
JH> currently i have it set to ignore all of these keys (see
JH> {ap_,DEC,HP,Sun}keysym.h). does anyone use these ??
JH> it wouldn't be hard for someone to add support for them,
JH> i just wasn't sure how widely they were used...
JH> jeff
JH> At 09:13 AM 5/28/99 -0500, Gisli Ottarsson wrote:
>> ...
>> Thank you for your response. Here is what I have learned:
>>
>> % echo "keycode 48 = dead_acute quotedbl" | xmodmap -
>>
>> The key in question now generates an acute accent in AbiWord and many
>> other applications including netscape, StarOffice 5.1, WordPerfect 8.0
>> and some of the GNOME text widgets, e.g. gEdit, GXedit, Terminal
>> et.al. Much better than what I had before.
>>
>> Xemacs, unfortunately, complains "Autoloading failed to define
>> function compose-acute-map". An alternative that is more to Xemacs'
>> liking:
>>
>> % echo "keycode 48 = SunFA_Acute quotedbl" | xmodmap -
>>
>> is totally useless in all the aforementioned applications but causes
>> my version of AbiWord to crash as described earlier.
>>
>> So, it would seem that I should switch from SunFA_Acute to dead_acute
>> which seems to be the more appropriate keysym (I'll figure out what is
>> eating Xemacs). Meanwhile, you will probably want to look at the
>> SunFA_Acute related crash.
>> ...
>> >>
>> >> System: RedHat 6.0
>> >> Version: abisuite-0.7.0-1.i386.rpm
>> >>
>> >> I send a dead acute accent, per the following KeyPress event
>> >>
>> >> KeyPress event, serial 18, synthetic NO, window 0x3800001,
>> >> root 0x26, subw 0x0, time 4159434140, (70,75), root:(1326,98),
>> >> state 0x0, keycode 48 (keysym 0x1005ff03, SunFA_Acute), same_screen YES,
>> >> XLookupString gives 0 characters: ""
>> >>
>> >> and abiword crashes with the following trace.