Re: Commands containing UTF8 characters mess up bash history

[Ryan Cunningham]

You could use the command "history -c" to clear the history in case this 
becomes a real issue. I don't have a real fix.

Sent from my iPad

> On Mar 1, 2014, at 1:23 PM, Yuri <yuri@rawbw.com> 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.
> 
> bash-4.2.45_1
> 
> Yuri
>