From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9365 invoked from network); 16 Feb 1997 15:06:24 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 16 Feb 1997 15:06:24 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id JAA04949; Sun, 16 Feb 1997 09:42:46 -0500 (EST) Resent-Date: Sun, 16 Feb 1997 09:42:46 -0500 (EST) From: gwing@primenet.com.au Message-ID: <19970216144443.9329.qmail@primenet.com.au> Subject: Re: Not *exactly* a bug, but ... To: schaefer@nbn.com Date: Mon, 17 Feb 1997 01:44:43 +1100 (EST) Cc: zsh-workers@math.gatech.edu In-Reply-To: <970214002444.ZM24515@candle.brasslantern.com> from "Bart Schaefer" at Feb 14, 97 00:24:43 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"n5TSm.0.GD1.cpn1p"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2899 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Bart Schaefer wrote: :I think I may have reported this before, a very long time ago ... :zsh% fc -W >(....) This for specific commands? It works for me, eg. fc -W >(cat) Are you getting this both in older and newer versions? zsh-3.0.0 up to 3.0.3-test3 work on my NetBSD machine. :This locks up zsh. You have to HUP it from another shell (or from the :xterm ctrl-btn1 menu) to kill it; there's no way to wake it up. -- Geoff Wing [gwing@primenet.com.au] Technical Manager Phone : +61-3-9818 2977 PrimeNet - Internet Consultancy Facsimile: +61-3-9819 3788 Web : Mobile : 0412 162 441