| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| To: | cygwin AT sourceware DOT cygnus DOT com |
| Subject: | Re: .bashrc strange behavior |
| References: | <19990719222351 DOT 13288 DOT rocketmail AT web107 DOT yahoomail DOT com> |
| Mime-Version: | 1.0 (generated by tm-edit 7.108) |
| From: | Ian T Zimmerman <itz AT lbin DOT com> |
| Date: | 19 Jul 1999 23:08:48 +0000 |
| In-Reply-To: | Earnie Boyd's message of "Mon, 19 Jul 1999 18:23:51 -0400 (EDT)" |
| Message-ID: | <87gc1lmtwf.fsf@amazon.lbin.com> |
| Lines: | 23 |
| X-Mailer: | Gnus v5.6.45/XEmacs 21.0(beta67) - "20 minutes to Nikko" |
>>>>> "Earnie" == Earnie Boyd <earnie_boyd AT yahoo DOT com> writes:
Earnie> This problem is related to the text vs binary issue. The
Earnie> user has the files mounted in binary mode. The .bashrc
Earnie> has \r\n (or text mode) line endings. The \r is being
Earnie> input into the buffer instead of removed causing the
Earnie> problems you are seeing.
Earnie> This is the reason I preach leaving the default text
Earnie> mounts and properly porting the code specifying the
Earnie> processing mode.
... but of course this wouldn't happen were .bashrc created by a
Cygwin program. They probably created it with Notepad or something.
IMHO there should be a fat warning about this in the User Guide. It
is mentioned there already, but too softly.
:-)
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |