From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7615 invoked by alias); 11 Oct 2017 06:41:52 -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: 41859 Received: (qmail 17930 invoked by uid 1010); 11 Oct 2017 06:41:51 -0000 X-Qmail-Scanner-Diagnostics: from mailout1.w1.samsung.com 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(210.118.77.11):SA:0(-6.9/5.0):. Processed in 3.637163 secs); 11 Oct 2017 06:41:51 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-AuditID: cbfec7ef-f79ee6d000003120-a4-59ddbd25705f Date: Wed, 11 Oct 2017 07:41:38 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: [BUG] In reference to patch 39815, about (z) flag and $( parse error Message-id: <20171011074138.52255215@pwslap01u.europe.root.pri> In-reply-to: <171010204917.ZM18524@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsWy7djP87qqe+9GGnxdwWZxsPkhkwOjx6qD H5gCGKO4bFJSczLLUov07RK4Mp42JhesZ634daSPqYFxHksXIyeHhICJRMPWP0wQtpjEhXvr 2boYuTiEBJYxSjSvvMkC4fQySex9dJ0ZpuPl1H5muKrdnxaxQzjTmCR+TJrJCuGcYZQ4ebQF KnOWUaKptR1sC4uAqsTzixfYQWw2AUOJqZtmM4LYIgLiEmfXnge7SlggWGLNzu1g9bwC9hLb uq+ygticAlYS8yZMAevlF9CXuPr3E9Tl9hIzr5xhhKgXlPgx+R7YHGYBHYlt2x6zQ9jyEpvX vAW7W0JgAZvEhIVz2CCaXST2df5lh7CFJV4d3wJly0h0dhyEWtDPKPGk2xeieQajxOkzO6Ca rSX6bl9khNjAJzFp23SgDRxAcV6JjjYhiBIPib2nN7BC2I4S3bsOQIP4GaPE8wlTWSYwKsxC cvgsJIfPQnL4AkbmVYwiqaXFuempxYZ6xYm5xaV56XrJ+bmbGIHJ4PS/4+93MD5tDjnEKMDB qMTDK3D9TqQQa2JZcWXuIUYJDmYlEd7qdXcjhXhTEiurUovy44tKc1KLDzFKc7AoifPaRrVF CgmkJ5akZqemFqQWwWSZODilGhgLy7TZJ1idSUw2z0oMfrJLXybijuu+Aq5O2bd2W173nQnw 2NnGbaGfLhlwjOvapOLjv7x1+1i1Dvul3b2daJW+LyNsE3NI1j+1pTtO/W9XL3O3dnDW17jj Xf/1Vq/pIefbhfYPkhvyXmXln/DqWtmrv+UwW0J0xe7HWtutfiqdCTp+2L5JSYmlOCPRUIu5 qDgRAMcjaqICAwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t/xK7oqe+9GGvzbqWhxsPkhkwOjx6qD H5gCGKO4bFJSczLLUov07RK4Mp42JhesZ634daSPqYFxHksXIyeHhICJxMup/cwQtpjEhXvr 2boYuTiEBJYwSvy+f4gdwpnBJPFx6ywo5xyjxN/lXUwQzllGidvf17KB9LMIqEo8v3iBHcRm EzCUmLppNiOILSIgLnF27XmwfcICwRJrn0wCq+EVsJfY1n2VFcTmFLCSmDdhCtSGZ4wS37uP gA3lF9CXuPr3ExPEgfYSM6+cYYRoFpT4Mfke2FBmAS2JzduaWCFseYnNa96CPSQkoC5x4+5u 9gmMwrOQtMxC0jILScsCRuZVjCKppcW56bnFhnrFibnFpXnpesn5uZsYgeG87djPzTsYL20M PsQowMGoxMMrcP1OpBBrYllxZe4hRgkOZiUR3up1dyOFeFMSK6tSi/Lji0pzUosPMUpzsCiJ 8/buWR0pJJCeWJKanZpakFoEk2Xi4JRqYMwo03j4VF+tXOXUxWtJ61s3n1imoutmwFOoZnFW 3k/nhmvy/JxdoscnaOgIrpzDuEPkj9h+tu/M5/afMu6clLhQ6n6I5/pvVhzP3J4yCln7vKyd xsO5WiH7xuZTjgznmthK582Pb16Xt33Kub/608RZpLZJCp9lnVNxUfnaBw32e0xLDj2I1lZi Kc5INNRiLipOBACqsbMcYwIAAA== X-CMS-MailID: 20171011064140eucas1p2ac0472237e227c9d15238b61125cc7d0 X-Msg-Generator: CA X-Sender-IP: 182.198.249.179 X-Local-Sender: =?UTF-8?B?UGV0ZXIgU3RlcGhlbnNvbhtTQ1NDLURhdGEgUGxhbmUb?= =?UTF-8?B?7IK87ISx7KCE7J6QG1ByaW5jaXBhbCBFbmdpbmVlciwgU29mdHdhcmU=?= X-Global-Sender: =?UTF-8?B?UGV0ZXIgU3RlcGhlbnNvbhtTQ1NDLURhdGEgUGxhbmUbU2Ft?= =?UTF-8?B?c3VuZyBFbGVjdHJvbmljcxtQcmluY2lwYWwgRW5naW5lZXIsIFNvZnR3YXJl?= X-Sender-Code: =?UTF-8?B?QzEwG0VIURtDMTBDRDA1Q0QwNTAwNTg=?= CMS-TYPE: 201P X-CMS-RootMailID: 20171011035004epcas4p16ed48cf97146739c4f8b12b9a7bd9340 X-RootMTR: 20171011035004epcas4p16ed48cf97146739c4f8b12b9a7bd9340 References: <171010204917.ZM18524@torch.brasslantern.com> On Tue, 10 Oct 2017 20:49:17 -0700 Bart Schaefer wrote: > So the doc says that (Z:n:) "causes unquoted newlines to be treated as > ordinary whitespace" but in fact what it really does is cause newline > *not* to be converted into a separator; it is still labeled as its > own separate token, which confuses this parse. > > The following fixes it, but it seems a hack -- is there a better way? To restrict it just to this case, you mean? It ought to be possible to detect specific flags. But as long as it does something plausible I don't think it matters. The way it sits on top of the lexical analyser is perpetual work in progress. pws