Bug 238186 - Typing å causes emacs to loop
Typing å causes emacs to loop
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chip Coldwell
Depends On:
  Show dependency treegraph
Reported: 2007-04-27 15:36 EDT by Kasper Dupont
Modified: 2008-05-06 18:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 18:13:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kasper Dupont 2007-04-27 15:36:17 EDT
Description of problem:
If you enter the letter å emacs enters an infinite loop

Version-Release number of selected component (if applicable):

How reproducible:
Happens every time

Steps to Reproduce:
1. Open an xterm
2. Type "emacs -nw filename"
3. Press ctrl-q
4. Type the letter å

Actual results:
Emacs enters an infinite loop

Expected results:
Emacs writes the letter å in the buffer

Additional info:
If I disable UTF-8, emacs works as intended.
Comment 1 Chip Coldwell 2007-04-27 15:40:09 EDT
Please try putting

(set-keyboard-coding-system nil)

in your .emacs.

See bug 205859.

Another alternative would be to install emacs-22.  A Fedora repo is available from

Comment 2 petrosyan 2008-05-06 18:13:26 EDT
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.

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