Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: output from bash not piped properly at startup
Message-ID: <8906161635.AA15888@aurel.caltech.edu>
Date: 16 Jun 89 16:35:58 GMT
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@ai.mit.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 37


   Date: Thu, 15 Jun 89 16:37:01 EDT
   From: Andrew Thomas <andrewt@watsnew.waterloo.edu>

   I reported this bug for 0.87, and it is still around in 0.99 so I
   thought I'd bring it up again.  I am running on a uVaxII with Ultrix
   2.0.

   watsnew> bash -norc
   bash> set | more
   bash> dirs
   ~
   bash> set | more
	   :
	   :
       all kinds of stuff
	   :
	   :
   bash>

   The problem:  If I try to pipe or redirect the output from any
   built-in bash command, then I get exactly nothing as the output
   (except, maybe, an EOF).  As soon as I do ANY builtin which sends any
   amount of output greater than nothing to the TERMINAL, then all pipes
   and redirects work properly.

   Does anybody else have this problem, or is it something specific to me
   (or Ultrix)?

I'm fixing this, although I haven't figured it out exactly.  It is
directly related to readline (); if you start the shell with

	bash -nolineediting -norc

you won't get this problem.

Brian