X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: strange problems with bash after cygwin update Date: Wed, 13 Dec 2006 17:13:53 -0000 Message-ID: <012201c71eda$10cf18a0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <45803444.9030604@freehackers.org> 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 13 December 2006 17:12, Philippe Fremy wrote: > Hi, > > My cygwin installation is pretty old, so I decided to update it. > Any idea what got broken during the update ? Nothing. Your scripts have /always/ had the wrong kind of line endings, it's just that something got fixed, to no longer accept them! Run 'd2u' on them or google the list archives for the new bash '(no)igncr' option. 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/