delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/01/31/16:03:22

From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: Re: ASCII and BINARY files. Why?
31 Jan 1997 16:03:22 -0800 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AF357.C94FDE40.8828.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: riche AT crl DOT com
Original-CC: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: The issue of modes on pipes would be much less of a problem if the
: mechanism for converting between DOS/Win text and C native
: text were a 1:1 mapping (i.e. NL->CRLF, CRLF->NL, CR->CR(always),
: (and LF->NL, but that's a side-issue)).  This way, if I want to pipe
: "gzip -dc file | tar xvf -" (as I often do), it wouldn't matter what mode
: the pipe was created in as  long as it was the same mode on both ends,
: because any changes introduced in a C->text conversion would be exactly
: reversed in the text->C conversion on the other end of the pipe.

Sounds good.
But how do you define LF vs. NL? I consider them to be the same.

I often use "tar cvvf - . | gzip > file".
[Your next paragraph about file redirection deleted]


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019