Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <20031125140640.47082.qmail@web21502.mail.yahoo.com> Date: Tue, 25 Nov 2003 06:06:40 -0800 (PST) From: Vince Rice Subject: wtfindex and dos line endings To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I reported a couple of weeks ago that wtfindex choked on text mounts, and Igor promptly fixed it (thanks, Igor!). I just discovered that wtfindex can't handle DOS line endings, even on text mounts. That is, the standard acronyms file (for example) has Unix line endings, and wtfindex now properly processes that file on either a binary or text mount. However, I created a new acronyms file yesterday with DOS line endings, and wtfindex produced a garbled file. Changing the file back to Unix line endings corrected the problem. So, I guess this could be a limitation or a bug, whichever you choose. :) @SRS8100:/home/vrice\> uname -a CYGWIN_NT-5.0 SRS8100 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown Cygwin @SRS8100:/home/vrice\> cygcheck -c wtf Cygwin Package Information Package Version Status wtf 0.0.4-5 OK Thanks, Vince __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- 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/