From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041016 Firefox/0.10.1 Description of problem: Searching of a string which contains e.g. a "[" or similar is not possible with a german keyboard. The search command is aborted as soon as AltGr is pressed. AltGr is necessary for some characters on german keyboards: @, �, {, }, [, ], \, �, ~, |, .. This is also an issue for RHEL-4. Version-Release number of selected component (if applicable): emacs-21.3-17 How reproducible: Always Steps to Reproduce: 1. Start emacs 2. Enter search string and press AltGr 3. Actual Results: Search aborts completely. Expected Results: Search string contains one of the above charaters. Additional info:
What is AltGr bound to in X for you? You say this is new in fc3? Looking through the changelog entries since fc2, I don't see anything that could have caused this directly. Could it be related to some change in xorg-x11?
Search is working for me on another box with emacs-21.3-14 and AltGr. After upgrading to 21.3-17 it is not working anymore.
You can reproduce with "emacs -q --no-site-file"?
Yes I can. It is still not working. "emacs -nw" is not affected.
What is AltGr bound to in X for you?
xev reports this for AltGr: KeyPress event, serial 30, synthetic NO, window 0x1800001, root 0xb6, subw 0x0, time 2515848786, (114,65), root:(117,841), state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 30, synthetic NO, window 0x1800001, root 0xb6, subw 0x0, time 2515849026, (114,65), root:(117,841), state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes:
Hmm, I see no changes in the changelog between -14 and -17 that could affect this. You don't think it is related to xorg-x11? Actually I just tried this with a RHEL4 beta and it seems to work fine for me. You can reproduce on a clean FC3 install?
Btw a similar bug has been reported for xemacs: bug 144601.
I have recompiled emacs-21.3-14. This version has the same porblem as emacs-21.3-17, but the original binary package emacs-21.3-14 does not have the problem.
Very strange... compiling on fc2 makes it work normally?
Here is the patch: http://lists.gnu.org/archive/html/bug-gnu-emacs/2004-10/msg00150.html It is working for me.
Thanks. However I'm having problems reproducing this now: 1) I install a fresh fc3 Personal Desktop 2) log into gnome after firstboot, 3) $ setxkbmap de $ emacs 4) press AltGr-8 and "[" appears without problem for me. What am I missing? (I don't doubt that there is a problem, but since I can't reproduce it is hard to test the fix...:)
The problem occurs only with I-search. Fire up emacs, hit Ctrl-S, then AltGr (no need to press anything else). Pressing AltGr terminates the search, so one cannot search for something that has eg. "[" in it.
Please have a look at the summary: "AltGr aborts search with Ctrl-S" ...
Yes, thank you. I just wanted to make sure this hasn't been fixed in newer xorg-x11, but it seems not for fc3 yet at least. And emacs doesn't build currently in devel...
emacs-21.3-20 in rawhide should have the above fix. Could you please test that first? Thanks.
The problem is fixed in rawhide emacs, but xemacs still has the problem. # rpm -q emacs xemacs emacs-21.3-20 xemacs-21.4.16-1
emacs-21.3-20 works for me.
For XEmacs, see bug 144601; it includes an attached fix that has already been applied upstream.
Thanks.
Re-opening for FC3 update.
Fixed in recent movemail security update.
*** Bug 139424 has been marked as a duplicate of this bug. ***