From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12376 invoked by alias); 30 Oct 2015 15:02:13 -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: 37024 Received: (qmail 1472 invoked from network); 30 Oct 2015 15:02:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=r+f9QLTHgb2+vN2X WQKGMxL053k=; b=X+Vz9v+ER5avOqtppqLWk4orn7VfmZdCCKUblrWw4DEClQ9R UqHbEHXjf7yk6hHpq/5BaSr3p+fFLrgu4Y8DwxYrBqgkULM72KNgDRdm3OLWiqVq c1xIKvNPBK3dogqiE3PtPj5Dq41yOitJW8r4YTyANWCNN42YdcAn5MoO+vU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=r+f9QLTHgb2+vN2 XWQKGMxL053k=; b=nnxBYbrKh2jXlUKu/8ExCC7kBd5NrqwafQno6GlsBINr6VB DmQsKoGR7xVqEk1S5G/nIFUWGeMzEl9I713LW8Z9rVVRWS5DwQhEcfPzWgvxCPWz iuTa/4OokLpc94AvTmu0i6WIqWbhuMKEVrbP+o3M0B27Yfowv00yrYr+AIzI= X-Sasl-enc: +o3wo3wNlmCZTmtvsBGkvYHjSTXgS845/mQJ2AEnd7ZH 1446217325 Date: Fri, 30 Oct 2015 15:02:03 +0000 From: Daniel Shahaf To: Peter Stephenson Cc: zsh-workers@zsh.org Subject: Re: Bug: bracketed-paste-magic + ztcp causes wrong pasted contents for CJK payloads Message-ID: <20151030150203.GB1462@tarsus.local2> References: <151027194317.ZM17099@torch.brasslantern.com> <151027202340.ZM17146@torch.brasslantern.com> <20151028093504.756c22b1@pwslap01u.europe.root.pri> <151028100744.ZM18361@torch.brasslantern.com> <20151028174448.70594180@pwslap01u.europe.root.pri> <151028163814.ZM1379@torch.brasslantern.com> <20151029093131.49241bde@pwslap01u.europe.root.pri> <20151029145143.6b3830a7@pwslap01u.europe.root.pri> <0D7C93CF-C84C-43BF-B7ED-4A868F04D401@kba.biglobe.ne.jp> <20151029165625.67eb2e43@pwslap01u.europe.root.pri> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20151029165625.67eb2e43@pwslap01u.europe.root.pri> User-Agent: Mutt/1.5.21 (2010-09-15) Peter Stephenson wrote on Thu, Oct 29, 2015 at 16:56:25 +0000: > On Fri, 30 Oct 2015 01:25:49 +0900 > Jun T. wrote: > > E01options.ztst also need be updated; otherwise it fails as follows: > > > > *** /tmp/zsh.ztst.err.65239 Fri Oct 30 00:54:52 2015 > > --- /tmp/zsh.ztst.terr.65239 Fri Oct 30 00:54:52 2015 > > *************** > > *** 1,3 **** > > --- 1,4 ---- > > fn:3: scalar parameter foo1 created globally in function > > fn:5: scalar parameter foo1 created globally in function > > fn:15: math parameter foo5 created globally in function fn > > + fn:15: numeric parameter foo5 created globally in function > > Hmmm... I must have been asleep when the math test was added, since > there's no reason at all why it should be inconsistent with the others. > Either report the function or not. > > -?fn:3: scalar parameter foo1 created globally in function > -?fn:5: scalar parameter foo1 created globally in function > -?fn:15: math parameter foo5 created globally in function fn > +?fn:3: scalar parameter foo1 created globally in function fn > +?fn:5: scalar parameter foo1 created globally in function fn > +?fn:15: numeric parameter parameter foo5 created globally in function fn Thanks for improving it ☺ I'll fix the "numeric parameter parameter" thing. > This ports the code to report the function. The math-specific code is > no longer needed now we have a check in setnparam(). I've been > overcautious since I can't see why we'd fail to find a function > on the trace stack if locallevel is non-zero. I can't see when that would happen, either; the reason for the NULL checks might be, more than anything else, that I wasn't familiar with the C funcstack data structure. Thanks, Daniel