From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: segfault in completion for configure
Date: Mon, 21 Mar 2016 10:56:11 +0000 [thread overview]
Message-ID: <20160321105611.57bf054a@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <160319190757.ZM28874@torch.brasslantern.com>
On Sat, 19 Mar 2016 19:07:57 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Specifically, if the signals arrive in order USR1 USR2 such that USR2
> is handled during the [[ ]] expression in TRAPUSR1, then the state from
> TRAPUSR2 will be discarded. I don't know if/how we ought to document.
Are you simply worried that a pattern match that happens asynchronously
might not leave behind $MATCH / $match etc. values after return owing to
other asynchronous goings on with pattern matching? I don't think
that's an issue. I'm sure there must be other examples of this.
pws
next prev parent reply other threads:[~2016-03-21 11:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 13:47 Vincent Lefevre
2016-03-11 14:32 ` Peter Stephenson
2016-03-11 23:00 ` Bart Schaefer
2016-03-12 3:11 ` Vincent Lefevre
2016-03-12 16:20 ` Bart Schaefer
2016-03-12 17:34 ` Bart Schaefer
2016-03-13 21:58 ` Vincent Lefevre
2016-03-15 2:43 ` Bart Schaefer
2016-03-17 13:43 ` Vincent Lefevre
2016-03-17 15:15 ` Vincent Lefevre
2016-03-17 18:13 ` Bart Schaefer
2016-03-17 19:55 ` Vincent Lefevre
2016-03-17 19:59 ` Vincent Lefevre
2016-03-17 15:24 ` Vincent Lefevre
2016-03-17 18:15 ` Bart Schaefer
2016-03-17 18:24 ` Peter Stephenson
2016-03-17 20:09 ` Daniel Shahaf
2016-03-17 21:49 ` Bart Schaefer
2016-03-20 2:07 ` Bart Schaefer
2016-03-21 10:56 ` Peter Stephenson [this message]
2016-03-21 15:26 ` Bart Schaefer
2016-04-05 12:49 ` Vincent Lefevre
2016-03-13 2:26 ` Vincent Lefevre
2016-03-12 2:56 ` Vincent Lefevre
2016-03-12 16:15 ` Bart Schaefer
2016-03-11 22:13 ` Daniel Shahaf
2016-03-12 2:58 ` Vincent Lefevre
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=20160321105611.57bf054a@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).