This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

My bash shell suddenly has "X-ray vision"


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. 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]