Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!cwns1!chet
From: chet@cwns1.CWRU.EDU (Chet Ramey)
Newsgroups: gnu.bash.bug
Subject: Re: bugs in bash 1.04 [SCO UNIX V/386 (3.2)]
Message-ID: <1990Feb26.225457.11380@usenet.ins.cwru.edu>
Date: 26 Feb 90 22:54:57 GMT
References: <270@txsil.lonestar.org>
Reply-To: chet@po.CWRU.Edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 18

In article <270@txsil.lonestar.org> steve@txsil.lonestar.org (Steve McConnel) writes:

$1) certain situations can get standard output swallowed up into never-never
$   land.  for instance ". foo >blort" sends not only the standard output of
$   foo's commands to blort, but the standard output of all following commands
$   (until the shell process is killed) to blort as well.  in some similar
$   situations, the builtin echo command prints out the accumulated standard
$   output from previous commands.  it's a bit unnerving having programs like
$   ls and cat silently appear to quit working... :-)

I have fixed this, and I sent the fix to Brian.

Chet
-- 
Chet Ramey				"Can't you pay a grad student to 
Network Services Group			 read the manual for you?"
Case Western Reserve University			-- Bill Wisner,
chet@ins.CWRU.Edu				   	to Peter Honeyman