X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-4.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RP_MATCHES_RCVD,TW_CG X-Spam-Check-By: sourceware.org Message-ID: <32994403.post@talk.nabble.com> Date: Sat, 17 Dec 2011 07:57:30 -0800 (PST) From: manu0507 To: cygwin AT cygwin DOT com Subject: Re: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed In-Reply-To: <20111217064104.GA7997@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <32989786 DOT post AT talk DOT nabble DOT com> <4EEC34F4 DOT 9090409 AT bopp DOT net> <20111217064104 DOT GA7997 AT ednor DOT casa DOT cgf DOT cx> 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 Dear Christopher, PLEASE read the three posts (the second one in particular) in the thread referenced below, and THEN decide who started the "rant". Thank you. Merry Christmas, Emanuel Christopher Faylor-8 wrote: > > On Sat, Dec 17, 2011 at 12:21:40AM -0600, Jeremy Bopp wrote: >>On 12/16/2011 11:13 PM, manu0507 wrote: >>>Notwithstanding the completely preposterous "reply" by Eric Blake (more >>>of an idiotic acrimony, actually) to my previous post (see >>>http://old.nabble.com/Igncr-ineffective--tt32983438.html ), there does >>>seem to be a problem in dealing with Win's CR/LF line endings in >>>"unusual" lines, at least on Win7-64 (or, to be really precise, on my >>>Win7-64). The lines where CR/LFs appear not to be properly converted >>>to LFs seem to be empty lines (except for the CR/LF, of course), as >>>well as some other "unusual" constructs (lines ending with ";;CR/LF" in >>>particular). >> >>I don't have Cygwin available at the moment, so I can't try running >>scripts as you describe right now. However, the claim that a line >>consisting of only a CR/LF causing problems with the igncr option makes >>me pretty suspicious. "Empty" lines are pretty darn common in bash >>scripts, and I would expect to have seen many reports of problems with >>igncr reported here by now if that option didn't correctly handle those >>lines. >>[...] > > Hats off to you, Jeremy, for your civility in responding to this rant. > > cgf > > -- > 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 > > > -- View this message in context: http://old.nabble.com/Sorry-%22people%22-%28NOT-MY-taxonomy%21%21%29%2C-but-igncr-IS-flawed-tp32989786p32994403.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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