Bug 144601 - AltGr/I-search problems in XEmacs
Summary: AltGr/I-search problems in XEmacs
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs   
(Show other bugs)
Version: 3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
Keywords: Patch
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-09 11:10 UTC by Ville Skyttä
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 21.4.16-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-27 16:17:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Workaround for X bug; fixes AltGr (341 bytes, patch)
2005-01-11 17:55 UTC, Ville Skyttä
no flags Details | Diff

Description Ville Skyttä 2005-01-09 11:10:34 UTC
I'm not sure which component is the culprit, but here goes:

The use of XEmacs and Emacs on FC3 is badly hindered by problems
related to the AltGr key.

Try starting a I-search in either (Ctrl-S), and try to search
something containing a character which requires the use of AltGr, for
example $ in my keyboard (Finnish) is AltGr+4.  In both editors, the
I-search quits immediately when AltGr is pressed, so such a search is
not possible.

Additionally, in XEmacs, only the AltGr press alone triggers the error
message "iso-level3-shift is not defined".

I googled for info, and found a suggested workaround for XEmacs:

  (define-key global-map [(iso-level3-shift)] #'ignore)

That gets rid of the above error message, but I-search still won't work.

I can input characters requiring the use of AltGr in both editors,
it's just the annoying error message in XEmacs + the I-search problem
in both that need solving.

I haven't had these problems earlier (eg. on FC2) with either editor.
 Upgrading XEmacs to the rawhide version does not help.  Ideas?

Comment 1 Jens Petersen 2005-01-11 06:54:48 UTC
See bug 137868 for the Emacs case.

As I commented there though (perhaps I'm missing something?)
it seems to work ok for me.  I don't normally use AltGr, but
with say

$ setxkbmap de
$ xemacs

I don't see any problems with AltGr.

Comment 2 Ville Skyttä 2005-01-11 07:50:02 UTC
On my box:

setxkbmap fi
/usr/bin/xemacs -vanilla
M-x set-variable debug-on-signal t
<press AltGr>

...results in:
Signaling: (undefined-keystroke-sequence [#<keypress-event

The same happens after "setxkbmap de".

Since this happens with both Emacs and XEmacs I suspect xorg.

Comment 3 Ville Skyttä 2005-01-11 07:51:40 UTC
(With Emacs there's no error from pressing AltGr as in above, but
I-search is aborted nevertheless.)

Comment 4 Ville Skyttä 2005-01-11 17:55:03 UTC
Created attachment 109626 [details]
Workaround for X bug; fixes AltGr

Based on bug 137868 comment 11, I came up with the attached patch for XEmacs
("xintrinsic.h" pulls in <X11/Xutil.h> via <X11/Intrinsic.h>).	Seems to work
for me, will send also upstream.

Comment 5 Ville Skyttä 2005-01-17 22:49:02 UTC
FYI, the patch from comment 4 was applied upstream to XEmacs 21.5, and is being
recommended for 21.4; it'll probably be in 21.4.17.  I think it would be good
and safe to apply it to the FC XEmacs package now.

Oh, and by the way, the GTK build of XEmacs has the same problem, but my patch
won't help with that.  Not a biggie AFAICS because XEmacs GTK 21.4 is not really
ready for much at all yet.

Comment 6 Ville Skyttä 2005-01-21 20:21:34 UTC
My patch for this has been applied upstream for both next XEmacs 21.[45] versions.

And in case you're interested, ditto a patch that fixes the same problem for the
GTK build: http://list-archive.xemacs.org/xemacs-patches/200501/msg00088.html

Could you rebuild a new XEmacs with at least the X patch applied for rawhide?  I
see the fixed GNU Emacs is already there...

Comment 7 Jens Petersen 2005-01-25 01:07:15 UTC
Sorry for the delay: your patch is in 21.4.16-2.

Comment 8 Ville Skyttä 2005-01-27 16:17:39 UTC
Works for me (tested on FC3).  Thanks.

Note You need to log in before you can comment on or make changes to this bug.