To: bug-bash@gnu.org
Subject: Commands containing UTF8 characters mess up bash history
Configuration Information:
Machine: amd64
OS: freebsd9.2
Compiler: clang
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='amd64'
-DCONF_OSTYPE='freebsd9.2' -DCONF_MACHTYPE='amd64-portbld-freebsd9.2'
-DCONF_VEND
OR='portbld' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -fno-omit-frame-po
inter -I/usr/local/include -O2 -pipe -fno-omit-frame-pointer
-fno-strict-aliasing
uname output: FreeBSD eagle.yuri.org 9.2-STABLE FreeBSD 9.2-STABLE #4
r260252M: Sat Jan 4 04:09:58 PST 2014 y...@eagle.yuri.org:/usr/obj/u
sr/src/sys/GENERIC amd64
Machine Type: amd64-portbld-freebsd9.2
Bash Version: 4.2
Patch Level: 45
Release Status: release
Description:
I manipulate with some files containing UTF8 characters. The
only commands I run are these:
./some-cmd < ../some-dir/utf8-containing-file-name.txt
vim ../some-dir/utf8-containing-file-name.txt
After a while of running of such commands, and going back and
forth in history and rerunning them, the history becomes messed up. The '
unkown character' question mark appears in the middle, some of them
become concatenated. History becomes unusable.
Repeat-By:
n/a
Fix:
n/a
