From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7202 invoked by alias); 13 Oct 2017 08:04:12 -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: List-Unsubscribe: X-Seq: 41874 Received: (qmail 3346 invoked by uid 1010); 13 Oct 2017 08:04:12 -0000 X-Qmail-Scanner-Diagnostics: from mail-qt0-f176.google.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(209.85.216.176):SA:0(-1.4/5.0):. Processed in 1.322915 secs); 13 Oct 2017 08:04:12 -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=-1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS, T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=aBVf0PelSHGZr9jl4Lci2DsKmvsW92Fpd9WsKG+dcEg=; b=KGbDcmtzETKCFKf/SHitvKSRFKrQwhMt9ZeK6ObznDuOUqJEdg4mXsS+Qi1KVJarbr jlxAP5+b1HKh1Tk1KZAd1S1mFdmvHTmwCQNp/LK++t6uFhHRkfHcu3OPYQw797iXb3b3 UCEUQAF89ZTUViLRyIoZ1HbR6sd2qMZaaC8ji9o4oTQMMd79T3t9rrqoXi905aXNjOGS CGg95DXtR2loBzLrhJD6S0pxOUTKjrCfQaUKw7i7JfhibOaRUxkYUYIOj4P++BTIRlif HpHJ5/3g3vrq2Ex04q++s/L2JwiY4uZXRbCzufIdM8Cb00oGeCrWcVyJeh7TIU+iSjB0 KxGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=aBVf0PelSHGZr9jl4Lci2DsKmvsW92Fpd9WsKG+dcEg=; b=nv86ZoM2QTwBmB1dC+r7HTsIzcztBhWNaDlBXfnCKOC19Ta1S7nkt3CF5EBSsUM/p/ 9IJQL0HW5w+bkTn0i792MtR1eizopz3BgnpZKSocTv3Q01vWj/DtUjiCYre+mFGEBbCB als+2ezHNExEnuSdiPJaymve2eqXa1j8b4jW8tse8egCMBAg3iK1KZVWJGFbNC/O9q/N s5OBxKVoM0zovvO6Vejw/wWyDcLwGYkIdMo2Yeu8de/FMos1thSa4bzwLyq7QBWTqqhG BB2fJd1lnMGG+03oPoVBF2isVSFZF34BlDMc91c1P1esdduZ/QSB1RokZB/+IrwvkpB3 F2Xw== X-Gm-Message-State: AMCzsaVTNrVMV/V/grIXrULvZL3sSxZtheeOu6G0Q4VW5++tT9OcTTF5 Akf2qhotqPOAj6LJ25Yf4Cxv830njqjMPdgK/OcGWg== X-Google-Smtp-Source: ABhQp+SWK0Xl5iqSBfR3DwdyDnhbC7S7cOozeYVWH9HHwcmVKXKbOrDcs4olnIpcsGQk6Wds9etBkeJ+XjuUdclS0BY= X-Received: by 10.237.33.186 with SMTP id l55mr829593qtc.71.1507881846690; Fri, 13 Oct 2017 01:04:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <171011100231.ZM3821@torch.brasslantern.com> From: Bart Schaefer Date: Fri, 13 Oct 2017 01:04:05 -0700 Message-ID: Subject: Re: [BUG] In reference to patch 39815, about (z) flag and $( parse error To: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Fri, Oct 13, 2017 at 12:53 AM, Sebastian Gniazdowski wrote: > > I was hoping that the goal of this patch wasn't exactly equal to what it did with (Z+cn+), i.e. that it accidentally changed the flag's behavior. That *is* what happened, but that doesn't always mean that it *directly* changed the behavior.