Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 24 Apr 2000 16:06:46 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: hybrid text/binary mount Message-ID: <20000424160646.F1469@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <200004241831 DOT OAA05979 AT envy DOT delorie DOT com> <20000424150424 DOT A1421 AT cygnus DOT com> <200004241934 DOT PAA06421 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <200004241934.PAA06421@envy.delorie.com>; from dj@delorie.com on Mon, Apr 24, 2000 at 03:34:10PM -0400 On Mon, Apr 24, 2000 at 03:34:10PM -0400, DJ Delorie wrote: >> I was thinking that if a file had any characters whose ASCII code was >> < ' ' or >= DEL before the first \n, then the file would be considered >> binary. Otherwise, the file would be text. You could apply this heuristic >> to both input and output. > >It's hard to apply it to output, because you don't know what the >program is going to write out. At least on input, you can read a big >chunk (buffering does this anyway) and run some tests on the existing >data. I think that most output is done in more than one character at a time mode. cgf