Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 69024 - Backspace handled incorrectly for non-English letters
Summary: Backspace handled incorrectly for non-English letters
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: bash
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: wdovlrrw
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: 65252 67218
TreeView+ depends on / blocked
 
Reported: 2002-07-17 05:59 UTC by Fred New
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-18 01:52:50 UTC
Embargoed:

Attachments (Terms of Use)

Description Fred New 2002-07-17 05:59:18 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)

Description of problem:
I don't know if this bug's "component" was correctly chosen.  This problem 
occurs in both the Gnome terminal and on the character console, so I chose a 
common denominator - bash:

When I type two non-English letters, such as 2 o-umlauts, then backspace twice, 
the first of the two letters still remains.

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


How reproducible:
Always

Steps to Reproduce:
1. Go to a Gnome terminal or log into a character console.
2. echo "<o-umlaut><u-umlaut><Backspace><Backspace>aa"
	

Actual Results:  <o-umlaut>aa

Expected Results:  aa

Additional info:

I installed Limbo with a English-US and Estonian languages, English-US is the 
default.  An Estonian keyboard is also installed.
Comment 1 Karsten Hopp 2002-07-23 15:02:10 UTC 
That's an bash/readline issue. Already fixed in the latest packages
Comment 2 Fred New 2002-07-24 09:01:43 UTC 
Yep.  I can confirm that this works correctly with bash-2.05a-16 recently 
installed from the Red Hat Network.
Note You need to log in before you can comment on or make changes to this bug.