From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Fwd: Re: [PATCH] isearch: do not use PAT_STATIC since we call zle hooks
Date: Tue, 10 Jan 2017 18:01:44 -0800 [thread overview]
Message-ID: <CAH+w=7b17T7v2TP_B-E7YCqQacTqSa1x+k9JUpLB-YEqsbsg7Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bXzCrfbnqx8g3a6zRrtJmTuoXn97NYOD67AkACRjziuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
Primenet vs. Gmail again.
---------- Forwarded message ----------
From: "Bart Schaefer" <schaefer@brasslantern.com>
Date: Jan 8, 2017 5:48 PM
Subject: Re: [PATCH] isearch: do not use PAT_STATIC since we call zle hooks
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Cc:
On Sun, Jan 8, 2017 at 5:35 PM, Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
>
> Is there a way to probe for this bug at runtime? I.e., a way for
> a script to determine whether the zsh binary that interprets it has or
> hasn't this bug?
You'd need something similar to the zpty-based Test/ scripts for
completion and vicmd, because you need to invoke interactive search
with a hook function.
For this specific bug, that is. One could probably devise by
examination of all uses of PAT_STATIC in the code base a test for the
more general case with trap handlers that I mentioned elsewhere in the
thread.
prev parent reply other threads:[~2017-01-11 3:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 17:25 m0viefreak
2017-01-06 17:35 ` Bart Schaefer
2017-01-08 19:33 ` Bart Schaefer
2017-01-08 19:40 ` Peter Stephenson
2017-01-28 19:02 ` Bart Schaefer
2017-01-28 19:15 ` Peter Stephenson
2017-01-28 19:39 ` Bart Schaefer
2017-01-28 19:47 ` Peter Stephenson
2017-01-29 0:01 ` Bart Schaefer
2017-01-29 16:24 ` Bart Schaefer
2017-01-09 1:35 ` Daniel Shahaf
2017-01-09 1:48 ` Bart Schaefer
2017-01-11 2:01 ` Bart Schaefer [this message]
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='CAH+w=7b17T7v2TP_B-E7YCqQacTqSa1x+k9JUpLB-YEqsbsg7Q@mail.gmail.com' \
--to=schaefer@brasslantern.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).