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 Date: Thu, 10 Apr 2003 21:26:47 +0100 Message-ID: <821-Thu10Apr2003212647+0100-starksb@ebi.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin AT cygwin DOT com Subject: FAQ help needed (Was: Bug? Mixed CR/LF and LF line endings from different programs) In-Reply-To: <20020830004815.GA25716@redhat.com> References: <20020829203820 DOT GB23580 AT redhat DOT com> <20020830001556 DOT 9D66C8B1F AT bellmann DOT research DOT canon DOT com DOT au> <20020830004815 DOT GA25716 AT redhat DOT com> From: David Starks-Browning Here's a blast from the past. OK, so now everyone knows that I'm 7 months behind in the cygwin mailing list. On Thursday 29 Aug 02, Christopher Faylor writes: > >which seems to contradict the Cygwin FAQ: > > > > It is rather easy for the porter to fix the source code by supplying > > the appropriate file processing mode switches to the open/fopen > > functions. Treat all text files as text and treat all binary files > > as binary. > > That section of the FAQ is out-of-date. Indeed, it is. (We're talking about the section "How is the DOS/Unix CR/LF thing handled?" in the API chapter of the FAQ.) Can anyone contribute a re-write of this section? The message I'm citing is at , in case you want to study the thread. Thanks, David (Cygwin FAQ maintainer) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/