From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8904 invoked by alias); 6 Aug 2017 19:18:05 -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: 41498 Received: (qmail 3079 invoked by uid 1010); 6 Aug 2017 19:18:05 -0000 X-Qmail-Scanner-Diagnostics: from know-smtprelay-omc-10.server.virginmedia.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(80.0.253.74):SA:0(-2.8/5.0):. Processed in 1.317217 secs); 06 Aug 2017 19:18:05 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: p.w.stephenson@ntlworld.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-Originating-IP: [86.21.219.59] X-Authenticated-User: p.w.stephenson@ntlworld.com X-Spam: 0 X-Authority: v=2.1 cv=SeoKDalu c=1 sm=1 tr=0 a=utowdAHh8RITBM/6U1BPxA==:117 a=utowdAHh8RITBM/6U1BPxA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=x7bEGLp0ZPQA:10 a=q2GGsy2AAAAA:8 a=NLZqzBF-AAAA:8 a=yrdhWlOopuS3rnihhxgA:9 a=CjuIK1q_8ugA:10 a=z9dJwno5l634igLiVhy-:22 a=wW_WBVUImv98JQXhvVPZ:22 Date: Sun, 6 Aug 2017 20:17:56 +0100 From: Peter Stephenson To: "zsh-workers@zsh.org" Subject: Re: Comment behaviour Message-ID: <20170806201756.3db5252a@ntlworld.com> In-Reply-To: References: <20170806191531.15dfad23@ntlworld.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1502047077; bh=lu34SoOTXY+NEAY0N7L0HezvhEELfYQDOIkVWQJAegU=; h=Date:From:To:Subject:In-Reply-To:References; b=5VOf/fC5/h1grLPd2odJYMMOHxAXAK0sleno61p6djXGsN6mb+CfcDCllaovnznZd uT44SLqh8c9VevCneOH2mPW2uh6z71URemWDKoiOvE8KyzQKZmeV5nd53y6pE328oX 4T4ooyfRBd8E4YLWxtDAcjrGNjD1W/p930lBCrpc6WZUXEifR77Q1YlnSOQJCBbeMp U3dLf+mndZB9VfESdsRe9C/ZwSkWDbfTSIj/yvs6acgeQ9BO66ULg1BdZys+zuHDUv LTLCEbDbHEzE6kMzadeaOlAAPvmwP3WbYJYBWOl+zQ/NAvQ1d82gro5EbqWK0ns1bm aFy1yQiXEzIbw== On Sun, 6 Aug 2017 11:59:53 -0700 Bart Schaefer wrote: > On Sun, Aug 6, 2017 at 11:15 AM, Peter Stephenson > wrote: > > > > I'll have a closer look after the release if this particular case can be > > treated differently, however --- it's clearly not useful to have it > > treated as a parse error if it's easy to do it otherwise. > > It's a parse error because "}#" is not a "}" token and the script > _ends_ after that, so no matching "}" is ever found. I don't think > you want to parse "}#" as two separate tokens. The question arises in this particular case because it's in command position so only certain special syntax is valid. But it seems like the following is currently valid, if stupid: % alias "}#"='echo "Hello"' % { cursh> }# cursh> } Hello so we can't change it without repercussions. pws