My bash shell suddenly has "X-ray vision"

Andy Koppe
Mon Sep 27 11:30:00 GMT 2010

On 27 September 2010 04:27, SJ Wright wrote:
>>> Or is it just the difference in encodings?
>>> In scripts and config/convenience files like .bashrc or .bash_aliases, it
>>> can
>>>  see *through* "crunches" (#), which are supposed to make a line of text
>>> invisible to a shell <or am I wrong on that?>
>>> Could it be because I added a LANG variable and have been turning out
>>> not-quite-UTF-8 stuff from my one or two text editors? The only guess I
>>> can
>>> make with my limited knowledge is that, once UTF8 is set or enabled,
>>> ISO-8859-1 "crunches," for all practical purposes, are meaningless to the
>>> shell.

To answer that part: no, UTF-8 vs ISO-8859-1 makes no difference to
that symbol, because it's part of the ASCII range, which is shared
between all of the character encodings supported by Cygwin.

> the mouseless approach vi and nano restrict one to.

They do you have some mouse support actually. Enable with ':set
mouse=a' in vim, and with Alt+m in nano.

> ~/.Xresources: Little-endian UTF-16 Unicode text, with CRLF line terminators

That one won't work, because UTF-16 is not ASCII-compatible.


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list