On 3/1/14, 4:23 PM, Yuri wrote:
> 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.
>
> I am sure you will be able to reproduce this. Otherwise is kind of hard to
> create a test case for this kind of problem. But I am sure bash doesn't
> treat command, or some part of it, as utf8, and confuses number of
> characters and number of bytes.
I can't reproduce this using bash-4.2.45 or bash-4.3 on Mac OS X or RHEL5.
I'm using Mac OS X Terminal, if that makes a difference.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
