problem with command editing when console is in unicode and history contains characters invalids in unicode

[Philippe Errembault]

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation
CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' 
-DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DL
OCALEDIR='//share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. 
-I./include -I./lib -g -O2
uname output: Linux Nestor 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 
i386 GNU/Linux
Machine Type: i686-pc-linux-gnu
Bash Version: 3.0
Patch Level: 0
Release Status: release


Description:
When console is in unicode and history contains characters sequences invalid in 
unicode (e.g. an ISO-8859 accented character) Then
this, character being undisplayable, will generate various kind of problems

remark :
This can arise when using autocomplete on iso8859 filenames. e.g. : you have a 
samba server with both iso8859 AND UTF-8 client and
you cannot use samba transcoding because you don't which coding is used by a 
specific workstation.


Repeat-By:
remark : indepently of the locale configuration you can type the 'é' character 
with the sequence [ALT-233] (press the ALT key, type
233 on the numeric keypad, release the ALT key - Hem... I know you know it, but 
well... to be sure ;-) )

Ok, Let's do it :
if started, stop the unicode support [1](unicode_stop)
create a file called file_iso-8859_é : [2](> file_iso-8859_[ALT-233])
type a very long command[3] (let's say at least 4 lines on your console) 
including the name of this file in the second line.
now start unicode support again [4](unicode_start)
Just for comparing, create a file called file_unicode_é : [5](> 
file_unicode_[ALT-233]
now fill the history with a few dummy commands [6...]
now browse you history back and forth up to and behond [3] and edit [3] to see 
how your editing zone gets garbaged