output from bash not piped properly at startup

Article View: gnu.bash.bug

Article #127

#127

From: Andrew Thomas
Date: Thu, 15 Jun 1989 20:37

29 lines
1248 bytes

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)?

Andrew Thomas
andrewt@watsnew.waterloo.edu	Systems Design Eng.	University of Waterloo
"If a million people do a stupid thing, it's still a stupid thing." - Opus

Technical Details

Message-ID: <8906152037.AA14414@watsnew.waterloo.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!WATSNEW.WATERLOO.EDU!andrewt

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!WATSNEW.WATERLOO.EDU!andrewt
From: andrewt@WATSNEW.WATERLOO.EDU (Andrew Thomas)
Newsgroups: gnu.bash.bug
Subject: output from bash not piped properly at startup
Message-ID: <8906152037.AA14414@watsnew.waterloo.edu>
Date: 15 Jun 89 20:37:01 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 29