Re: How come i wrote a NO-BREAK SPACE in xterm+bash ?

[David Wright <deblis@lionunicorn.co.uk>]

Quoting Thomas Schmitt (scdbackup@gmx.net):

> Finally i found out that the refusing command line does not
> have an ASCII Blank (decimal 32) before the pipe symbol
> but rather UTF-8 code (194,160) which means U+00A0
> "NO-BREAK SPACE".
> Obviously this does not count as whitespace in bash (vanilla
> Debian 8.1 install). The error message had (194,160) between
> ".." and ":".
> 
> Now i riddle how my chair, my US-ASCII keyboard, and the
> problem inbetween managed to produce such a character
> in the bash (libreadline) command line of an xterm.
> 
> Does anybody have an idea how to reproduce this ?
> (In order to better avoid it.)

I just typed ls .. .. and I got two listings of ..
so then I tried Alt-Space and that's enough:
ls .. ..
ls: cannot access .. ..: No such file or directory
so I think you'll have the problem every once in a while.

Cheers,
David.