From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18489 invoked by alias); 31 Jul 2014 16:20:20 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32924 Received: (qmail 26323 invoked from network); 31 Jul 2014 16:20:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140731092023.ZM16680@torch.brasslantern.com> Date: Thu, 31 Jul 2014 09:20:23 -0700 In-reply-to: <20140731092711.GA28401@chaz.gmail.com> Comments: In reply to Stephane Chazelas "$(...) and <<" (Jul 31, 10:27am) References: <20140731092711.GA28401@chaz.gmail.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: $(...) and << MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jul 31, 10:27am, Stephane Chazelas wrote: } } $ zsh -c 'echo $(cat << EOF } blah) } EOF } ); echo test' } zsh:4: parse error near `)' Yeah, to fix that we're going to have a write a whole new chunk of parser (lexer, really) specifically for $(...). There's an entry point for it now, but all it does is try to lexically consume a string ending with ")"; it handles balanced paren pairs but not the situation above. Same with % echo $(case $foo in bar) echo test;; zsh: parse error near `;;' } By the way, is there any plan of having an issue tracker for } zsh somewhere. That would help to keep track of the known } issues. An issue tracker needs to be part of a larger plan -- we tried using the tracker at SourceForge but it didn't work because no one monitors it, so it became an issue black hole. At the moment there isn't anyone to take that responsibility.