From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24622 invoked by alias); 12 Feb 2015 16:44:09 -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: 34517 Received: (qmail 3165 invoked from network); 12 Feb 2015 16:43:55 -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 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=I4zSn2kl c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=0HtSIViG9nkA:10 a=qGfdgLGw11Lo4BlvV-4A:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <150212084323.ZM20337@torch.brasslantern.com> Date: Thu, 12 Feb 2015 08:43:23 -0800 In-reply-to: <20150212092536.74db3b50@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: completion problem with '291' ok with '274'." (Feb 12, 9:25am) References: <54DA87F5.5090303@eastlink.ca> <150210183520.ZM16470@torch.brasslantern.com> <54DACEF7.90605@eastlink.ca> <150210202035.ZM16595@torch.brasslantern.com> <54DAF251.4040702@eastlink.ca> <150211082827.ZM17558@torch.brasslantern.com> <54DB93F2.6090202@eastlink.ca> <54DBE5BF.3020609@eastlink.ca> <54DC0675.4040808@eastlink.ca> <54DC34EF.4010204@eastlink.ca> <150211213054.ZM19450@torch.brasslantern.com> <20150212092536.74db3b50@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: completion problem with '291' ok with '274'. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 12, 9:25am, Peter Stephenson wrote: } Subject: Re: completion problem with '291' ok with '274'. } } On Wed, 11 Feb 2015 21:30:54 -0800 } Bart Schaefer wrote: } > So basically we have to back out all of 34485 and start that over. } } Yes, it's job control stuff that the test suite doesn't cover. So I should go ahead and commit that back-out? } Removing the tests in front of the "*cmplx = 1" must be safe in the } sense that if it shows up problems for annonymous functions then they're } already present in the standard execution path and hence need fixing. I thought we determined before that there's some sort of interaction between the wordcode generation and the setting of *cmplx such that one can't just change the way that value is computed in par_simple() et al. without making a corresponding change upstream? I'm probably mis-remembering.