X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 26 Apr 2012 10:26:32 -0400 Message-ID: Subject: Re: Odd behavior of scripts in dos mode From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 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 Thu, Apr 26, 2012 at 10:13 AM, Andrew DeFaria wrote: > I remember that Cygwin used to not be able to run scripts that were > converted or were in "DOS" mode - had trailing carriage returns in the file. > It would fail because the #! line might have /bin/bash\r which was not a > file (bash with a carriage return that is). But the behavior has changed. > Now it seems to ignore the trailing carriage return and it execs bash > itself. But it fails later on with other carriage returns. http://cygwin.com/faq/#faq.api.cr-lf -- Earnie -- https://sites.google.com/site/earnieboyd -- 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