From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24603 invoked from network); 18 Apr 1998 17:23:11 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 18 Apr 1998 17:23:11 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id NAA15231; Sat, 18 Apr 1998 13:04:38 -0400 (EDT) Resent-Date: Sat, 18 Apr 1998 13:04:38 -0400 (EDT) From: "Bart Schaefer" Message-Id: <980418030434.ZM3820@candle.brasslantern.com> Date: Sat, 18 Apr 1998 03:04:34 -0700 X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@math.gatech.edu Subject: Pipeline process wait bug in 3.0.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"PzPO93.0.wj3.cqDEr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3843 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu I have this little function: isset () { setopt | grep -i $(echo $1 | tr -d _) } This is so I can type e.g. zsh% isset auto_cd autocd on However, a bit less than half the time, running this function produces zsh% isset autocd zsh% autocd on (with the cursor now at the beginning of the next line). I can't be sure, of course, but it seems to me this must be a problem with zsh failing to wait for the entire pipeline to complete before it prints the next prompt. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com