delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1996/10/21/18:39:24

From: jcook AT mseng DOT kla DOT com (John Cook)
Subject: re: using cat on binary files (CTRL-Z trauma)
21 Oct 1996 18:39:24 -0700 :
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <326BF9F5.cygnus.gnu-win32@mscorp.kla.com>
Original-To: "'gnuwin32'" <gnu-win32 AT cygnus DOT com>
Encoding: 26 TEXT
X-Mailer: Microsoft Mail V3.0
Original-Sender: owner-gnu-win32 AT cygnus DOT com

On Fri, 18 Oct 1996, root wrote:

> Date: Fri, 18 Oct 1996 22:55:31 -0700
> From: root <root AT jacob DOT remcomp DOT fr>
> Subject: Re: using cat on binary files (CTRL-Z trauma)
> >
> > When I try to cat a binary file, cat bails upon receiving
> > the first CTRL-Z byte.  CTRL-Z is the DOS end-of-file character
> > (right?)

> Wrong!
> DOS doesn't use the Ctrl-Z character since (at least) DOS 3.X
> i.e. several centuries ago in this rapEEdly moving field! We are
> now in DOS Windows NT style, quite a change since C:>

Thank you for this clarification...  I am still looking for an answer
to my main question, however:  Is there a way to prevent cat from
quitting when it finds a CTRL-Z in its input under either the Win32
console or GnuWin32 bash?

....And if CTRL-Z is _not_ an EOF character, then why does cat behave
this way within Windows NT?  Is cat not intended for binary files under
Win32 environments?

John Cook
-
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