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 melb.werple.net.au (8.7.5/8.7.3) with ESMTP id EAA11944 for <mason@werple.mira.net.au>; Fri, 26 Apr 1996 04:39:38 +1000 (EST)
Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA09582; Thu, 25 Apr 1996 14:11:53 -0400 (EDT)
Resent-Date: Thu, 25 Apr 1996 14:11:53 -0400 (EDT)
From: Anthony Heading <aheading@jpmorgan.com>
Message-Id: <199604251810.TAA00347@gmp-etpres1.uk.jpmorgan.com>
Subject: echo $(wc <(wc /vmunix) <(wc /vmunix))
To: zsh-workers@math.gatech.edu
Date: Thu, 25 Apr 1996 19:10:47 +0100 (BST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"3yDT_3.0.bL2.e1yVn"@euclid>
Resent-From: zsh-workers@math.gatech.edu
X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/958
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

The command in the subject line: `echo $(wc <(wc /vmunix) <(wc /vmunix))' locks up
zsh (at least my version 2.6-beta13-hzoli13 on SunOS 4.1.3) when ^C is hit immediately
after hitting return.  I'm afraid I've no idea why, but it's obviously a bit tedious.
Maybe I'll use =(...) instead - that seems to work ok.

Anthony