Bug 238186 - Typing å causes emacs to loop
Summary: Typing å causes emacs to loop
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Coldwell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-27 19:36 UTC by Kasper Dupont
Modified: 2008-05-06 22:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-06 22:13:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kasper Dupont 2007-04-27 19:36:17 UTC
Description of problem:
If you enter the letter å emacs enters an infinite loop

Version-Release number of selected component (if applicable):
emacs-21.4-17.3.fc6

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 19:40:09 UTC
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

http://people.redhat.com/coldwell/emacs/fedora/


Comment 2 petrosyan 2008-05-06 22:13:26 UTC
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.