output from bash not piped properly at startup

Thread View: gnu.bash.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Brian Fox Fri, 16 Jun 1989 16:35

#13

Author: Brian Fox
Date: Fri, 16 Jun 1989 16:35

37 lines
1450 bytes

   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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads