X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: CR/LF problems after upgrade Date: Fri, 5 Jan 2007 11:43:09 -0000 Message-ID: <012901c730be$ac6ca7f0$0708090a@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <8174573.post@talk.nabble.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 05 January 2007 08:33, fschmidt wrote: > After I upgraded cygwin, my scripts stopped working. I see that this has > something to do with a change in how bash treats CR/LF and I see a lot of > old discussion on this topic, none of which I understand. I am not > interested in understanding the details, I just want my scripts to work. So > can I either go back to an old version of cygwin before this change, or can > I add some commands to my /etc/profile to make my scripts work? Any help > would be appreciated. It's dead simple: just use the 'd2u' program on your script files, it will convert the line-endings from dos to unix format and everything will be fine. Alternatively, there is a shell option for recent versions of bash called 'igncr' that persuades it to ignore CR when it finds one at the cost of a bit of slowdown executing scripts. See item #4 in the recent bash release announcements. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/