On 12/17/14, 4:40 PM, Lars-Daniel Weber wrote:
> Hi there,
>
> has this bug already been solved?
> http://unix.stackexchange.com/questions/22435/how-to-fix-character-encoding-in-bash-arch-linux
Yes. It's not really a bug, more of an implementation issue. Bash-4.2
changed the way command-not-found was reported: it encoded non-printable
characters (as reported by isprint(3)) to avoid printing gibberish to the
terminal. Bash-4.3 improved the handling of printable characters for
which isprint() returns false, mostly multibyte characters.
According to the change log, this went in in the 2011-08-19 snapshot.
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/
