X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4CA00F16.6030407@charter.net>
References: <4C9EA18E.4060903@charter.net>	<4C9FF0FF.3080506@cygwin.com>	<4CA00F16.6030407@charter.net>
Date: Mon, 27 Sep 2010 05:46:37 +0100
Message-ID: <AANLkTinoh_7F0rTPMDPVBUkL=op4RhOpcBQXCsnMpmsP@mail.gmail.com>
Subject: Re: My bash shell suddenly has "X-ray vision"
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

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
>>> =C2=A0see *through* "crunches" (#), which are supposed to make a line o=
f 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 t=
he
>>> 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=3Da' in vim, and with Alt+m in nano.

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

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

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple