From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.5/8.7.3) with ESMTP id WAA10798 for ; Thu, 19 Sep 1996 22:14:11 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id IAA11163; Thu, 19 Sep 1996 08:00:17 -0400 (EDT) Resent-Date: Thu, 19 Sep 1996 08:00:17 -0400 (EDT) From: whukriede@ifm.uni-kiel.d400.de Date: Thu, 19 Sep 1996 13:59:16 +0200 Message-Id: <9609191159.AA12685@xerxes.ifm.uni-kiel.de> To: pws@ifh.de Subject: Re: more on pipe bug Cc: whukriede@ifm.uni-kiel.d400.de, zsh-workers@math.gatech.edu Resent-Message-ID: <"tw7Ru1.0.Lk2.GNJGo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2151 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Hi! > I've made some progress. The simplest form required to show the bug > is something like: > % if true; then echo | more; fi The bug seems to have been in 2.5.03 already: zsh-2.5.03> if true ; then cat some-file | more ; fi ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C ^Z^Z^Z [ ... nothing happens ...] [then after killing the (btw busy!) more-process:] zsh: 1060 interrupt cat some-file | zsh: 1061 terminated more zsh-2.5.03> So long, Wolfgang.