X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Sun, 20 Apr 2008 08:10:01 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: bash script works on one PC, bombs on another? In-Reply-To: <943be0b10804191330y485bdcfflcbbf7688ccfaf2f7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <943be0b10804181948t509e7a6cg189229e568ba03fc@mail.gmail.com> <48097839.F9B4831@dessent.net> <943be0b10804191330y485bdcfflcbbf7688ccfaf2f7@mail.gmail.com> X-Google-Sender-Auth: ada17dbdb29290f9 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Apr 19, 2008 at 4:30 PM, Dave Burns wrote: > I considered that, and edited the file using vim, and retyped that > line. Is that enough to eliminate that possibility? Nope, vim will happily preserve the line-ending convention of the file. Look for an indicator in the status line - "(text)" or "(text mode)" or "(DOS)" or something, don't recall offhand. That means it has CRLF's. You can fix it by typing :set notextmode and then writing it back out. Or, as Gary said, run d2u on it. -- Mark J. Reed -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/