From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-12233-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 2441 invoked from network); 12 Jul 2000 11:12:25 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 12 Jul 2000 11:12:25 -0000
Received: (qmail 8898 invoked by alias); 12 Jul 2000 11:12:08 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 12233
Received: (qmail 8889 invoked from network); 12 Jul 2000 11:12:07 -0000
Date: Wed, 12 Jul 2000 12:11:40 +0100
From: Peter Stephenson <pws@cambridgesiliconradio.com>
Subject: Re: Bug in ${(z)...} lexing, or what?
In-reply-to: "Your message of Wed, 12 Jul 2000 12:47:27 +0200."
 <200007121047.MAA21893@beta.informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Message-id: <0FXL00LET0FF5Y@la-la.cambridgesiliconradio.com>
Content-transfer-encoding: 7BIT

>   % a='[[ a = (#i)foo ]]'
>   % print -l ${(z)a}
>   [[
>   a
>   =
>   (
>   #i
>   )
>   foo
>   ]]

Strange, I get (#i)foo on one line, even with zsh -f.  There must be some
unexpected option dependence, but I can't see what.

-- 
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070