X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org X-Authority-Analysis: v=1.0 c=1 a=TrlYx4XE_7UA:10 a=8nJEP1OIZ-IA:10 a=p_4CpwLqXbWGGTx1YloA:9 a=d-COO-OaORdBqKvp1JUA:7 a=FYuwOgXncRfRV_ZFZFz0HvYyEnsA:4 a=wPNLvfGTeEIA:10 Message-ID: <4C9EA18E.4060903@charter.net> Date: Sat, 25 Sep 2010 21:27:42 -0400 From: SJ Wright User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: Cygwin User Mailing List Subject: My bash shell suddenly has "X-ray vision" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 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. or am I wrong on that as well? A little help, please. This isn't making a whole lot of sense. What good are rules for comments if, when a new text encoding or environment variable is applied/undertaken/invoked, they become null and void? (Might as well go back to REM: from CLI BASIC.) Steve W -- 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