On 03/10/12 16:52, Tarl Neustaedter wrote:
ASCII didn't have the upper bit, so >= 0x80 would be more correct. Does this correspond to any "upstream" that we should patch as well?
Since rubout (0x7f) is also not representable, "ustr[1] >= 0x7f" might be even better.
That's fine with me. It was mainly because some of the "special" directories contained low ASCII which was moving the console cursor around and hence corrupting the display output.
ATB,
Mark.