From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug: bracketed-paste-magic + ztcp causes wrong pasted contents for CJK payloads
Date: Thu, 29 Oct 2015 09:31:31 +0000 [thread overview]
Message-ID: <20151029093131.49241bde@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <151028163814.ZM1379@torch.brasslantern.com>
On Wed, 28 Oct 2015 16:38:13 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Oct 28, 5:44pm, Peter Stephenson wrote:
> }
> } I wonder if the existing setsparam() etc. functions, which are currently
> } just aliases or front-ends for assignsparam() etc. with no warnings,
> } could be modified to add the flag based on the option?
>
> You mean modify the implementations, not the call signature, correct?
Yes.
> Testing of the WARNCREATEGLOBAL flag is pretty isolated at the moment
> and there are a lot of calls to setsparam() et al.
Exactly. I suspect they could all benefit --- I can't think of a case
where this is actually wrong, only where you don't care. But
WARNCREATEGLOBAL isn't supposed to care whether your care, only warn...
pws
next prev parent reply other threads:[~2015-10-29 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:54 Chi Hsuan Yen
2015-10-15 20:54 ` Bart Schaefer
2015-10-16 0:25 ` Bart Schaefer
2015-10-16 19:40 ` Chi Hsuan Yen
2015-10-18 15:52 ` Bart Schaefer
2015-10-18 16:19 ` Chi Hsuan Yen
2015-10-28 2:43 ` Bart Schaefer
2015-10-28 3:23 ` Bart Schaefer
2015-10-28 9:35 ` Peter Stephenson
2015-10-28 17:07 ` Bart Schaefer
2015-10-28 17:44 ` Peter Stephenson
2015-10-28 23:38 ` Bart Schaefer
2015-10-29 9:31 ` Peter Stephenson [this message]
2015-10-29 14:51 ` Peter Stephenson
2015-10-29 15:00 ` Bart Schaefer
2015-10-29 15:10 ` Peter Stephenson
2015-10-29 16:25 ` Jun T.
2015-10-29 16:56 ` Peter Stephenson
2015-10-30 15:02 ` Daniel Shahaf
2015-11-03 16:31 ` Chi Hsuan Yen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151029093131.49241bde@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).