X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <32989786.post@talk.nabble.com> Date: Fri, 16 Dec 2011 21:13:36 -0800 (PST) From: manu0507 To: cygwin AT cygwin DOT com Subject: Sorry "people" (NOT MY taxonomy!!), but igncr IS flawed MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi all, 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). To work around the problem, I'm writing an application that would convert all CR/LF-ending text files into LF-ending ones... but it's not really trivial, because telling binary files that should be left untouched from text files that should be converted is difficult: even the very first file in GDB's sources ("configure") contains a '\a', i.e. a "not-text" byte. I don't think that believing that anybody who knows anything beyond Unix/Linux must surely be an idiot (as Blake seems to suggest) is constructive - after all, we all strive to produce applications that would make a difference, whatever the platform. Cygwin is a beautiful piece of work, no doubt about it... but believing it's bug-free just because it's inspired by Unix/Linux is counter-productive at best, and preposterous at worst. So, to get back to the real subject: is there a correction to be had to the CR/LF problem? Many thanks, Emanuel -- View this message in context: http://old.nabble.com/Sorry-%22people%22-%28NOT-MY-taxonomy%21%21%29%2C-but-igncr-IS-flawed-tp32989786p32989786.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