From: ggp AT informix DOT com (Guy Gascoigne - Piggford)
Subject: RE: Why text=binary mounts
20 Jan 1998 09:21:35 -0800
Message-ID: <3.0.3.32.19980119100732.01c36e98.cygnus.gnu-win32@pop.pdx.informix.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19980115235518 DOT 03bc0e40 AT popd DOT ix DOT netcom DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Jeffrey C. Fried" <Jeff AT Fried DOT net>,
        Richard Thomas <richard AT smartmedia DOT co DOT uk>, gnu-win32 AT cygnus DOT com

At 11:55 PM 1/15/98 -0700, Jeffrey C. Fried wrote:
>That is, if we can agree that certain tools are always applied solely to
>text, then automatic conversion of the native EOL to the single '\n'
>character is the solution which will make these tools work in any
>environment.  If we don't agree, then we must always construct 'text' files
>according to the UNIX description of a text file when using the gnuwin32
>tools and so it is not easy to use tools of mixed origin on a non-UNIX
>system (for example emacs under NT will rewrite files with CRLF while bash
>will need these files in LF format).  I prefer to use the native format so
>that i don't have to remember which tools produce which results and when i
>have to convert between the two formats.

Good points, I agree with them completely.

Guy


-- 
Guy Gascoigne - Piggford (ggp AT informix DOT com)
Software Engineer, Informix Software, Inc. (Portland, Oregon)

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".