X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Gary R. Van Sickle" To: References: Subject: RE: [ANNOUNCEMENT] Updated: bash-3.2.39-19 Date: Sun, 4 May 2008 05:50:03 -0500 Message-ID: <000101c8add4$9c0319a0$020aa8c0@DFW5RB41> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: 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 > From: Eric Blake [] > 4. This version of bash has a cygwin-specific shell option, > named "igncr" > to force bash to ignore \r, independently of cygwin's mount > style. As of bash-3.2.3-5, it controls regular scripts, > command substitution, and sourced files. I hope to convince > the upstream bash maintainer to accept this patch into the > future bash 4.0 even on Linux, rather than keeping it a > cygwin-specific patch, but only time will tell. First the *government* sends *me* a check, now the first glimmer of hope appears in solving the heretofore-assumed-NP-complete text file line ending problem which has plauged computer science since prehistoric times. Man I love living in the future. Thank you Eric for your doggedness in getting this implemented and (hopefully) accepted. Here's hoping this can default to "on" upstream. -- Gary R. Van Sickle -- 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/