From: kkont AT estia DOT iit DOT nrcps DOT ariadne-t DOT gr (Kimon Kontovasilis) Subject: Re: Piped Commands Loss Of Output 4 Dec 1997 05:34:44 -0800 Message-ID: <9712041237.AA09143.cygnus.gnu-win32@estia.iit.nrcps.ariadne-t.gr> References: <34856BB1 DOT 68CC2642 AT boxhill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: jt AT boxhill DOT com (Jason Tishler) Cc: gnu-win32 AT cygnus DOT com > > Has anyone noticed a transient loss of output with piped commands > similar to the following: > > $ fgrep export .bashrc | wc > 12 30 339 > $ fgrep export .bashrc | wc > $ > Yes, I 've observed it too. > >From the above examples, I conclude that sometimes I get all output, > no output, and some output. > I experience the same random behavior; it happens only from within bash. (When I use 4DOS.COM, I don't get problems; I cannot be decisive about COMMAND.COM, since I don't use it frequently.) > I am using b18 with Sergey's coolview 25 Nov 97. I seem to remember > that I began to observe this problem when I upgraded to one of Sergey's > coolview ?? Sept 97 versions. Has anyone observed this too? Anyone > know whats wrong? > I use Win95 + b18 + coolview of Nov. 03, 1997. (Is your Nov. 25 version different? I didn't notice an announcement for anything newer from what I have. If yes, what are the differences?) Bye, Kimon. - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".