catting random bytes causes character craziness

I can't reproduce this at the moment, but I've seen it a number of times. What happens is, I'll end up catting a binary file into a *shell* buffer by mistake (e.g., by invoking wget with -O- and forgetting to pipe it somewhere) and when I kill that process, the characters printed in the shell buffer have gone into Crazy Mode. Like, I'll type "pwd", and instead of it looking like <jwz＠grendel:/tmp/> pwd /tmp <jwz＠grendel:/tmp/> It will look like ＠#!#$^%^%%(＠!!$$%%＠ pwd ,<$^ ＠#!#$^%^%%(＠!!$$%%＠ (but not those exact characters.) In other words, the shell is running programs properly, but everything it prints out is getting garbled. Running /usr/bin/reset does not fix matters; all I can do is kill that shell buffer. I'm guessing that what is going on is that some particular sequence of bytes is putting the shell into a Be-Crazy-Unicode mode or something, when clearly, no shell output should be interpreted with such semantics. I've definitely seen this with 21.1.14 several times. I have not yet seen it with 21.4.8, but I've only been using that one for a few days. -- Jamie Zawinski jwz(a)jwz.org http://www.jwz.org/ jwz(a)dnalounge.com http://www.dnalounge.com/