X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: bash-3.1-7 BUG Date: Wed, 13 Sep 2006 13:05:28 -0700 Lines: 12 Message-ID: References: <091320060438 DOT 11140 DOT 45078B490008FD8600002B8422007610640A050E040D0C079D0A AT comcast DOT net> <20060913052510 DOT GB1256 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Thunderbird/1.5.0.5 Mnenhy/0.7.3.0 In-Reply-To: X-IsSubscribed: yes 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 Eric Blake wrote: > But I intend that on binary files, \r\n > line endings will treat the \r as part of the line, so at least binary mounts > won't suffer from the speed impact of treating a file as unseekable the way > bash 3.1-6 does. Would it be possible to do this dynamically (instead of keying off of mounts, etc.): if the first line of the file read by bash has a \r\n, use text-mode (1-char-at-a-time) semantics, else use binary semantics (lseek)? -- 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/