X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 26 Oct 2006 18:00:27 -0400 From: "Lev Bishop" To: cygwin AT cygwin DOT com Subject: Re: igncr vs text mode mounts, performance vs compatibility In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1160655422743 DOT antti DOT nospam DOT 1605718 DOT wGO_WJ9D1NlId3tB-z6Qig AT luukku DOT com> <452F8719 DOT 9060300 AT cygwin DOT com> <4536BC88 DOT 3030003 AT qualcomm DOT com> <4536C922 DOT 4090807 AT qualcomm DOT com> <45376CBF DOT 1030104 AT byu DOT net> <453EA9C1 DOT 8060402 AT byu DOT net> <45401C68 DOT 7080706 AT byu DOT net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 One additional thing I'd like to say, if people are considering possibly making a decision based off the line ending of the first line of the file: it's worth bearing in mind that it's quite possible for a file to end up with mixed line endings. Most editors are at least smart enough to convert the whole file to their preffered format, but not all, and there's always the possibility of nastiness like: C:\TEMP> echo "extra line" >> file_with_unix_line_endings It's yet another special case to think of: "Why my scrpt not wrok?" "Because it is on a binary mount && you didn't set igncr && you have CRLF line endings on some lines && the first line doesn't have a CRLF" It'll be one of those things that works 99% of the time for 99% of people, and by the time it bites someone they'll have forgotton all about this issue and will be very confused. -- 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/