From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: precmd: write error: interrupted
Date: Sun, 5 May 2013 10:53:07 -0700 [thread overview]
Message-ID: <CAH+w=7Zdkq0St4cjCaFuEUmqYSTXjunSA=e_cx92gDCM9Y5L3g@mail.gmail.com> (raw)
In-Reply-To: <87y5btahrj.fsf@ft.bewatermyfriend.org>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Sun, May 5, 2013 at 2:38 AM, Frank Terbeck <ft@bewatermyfriend.org>wrote:
> I've pushed this, because it's definitely an improvement. I tried
> looking for the right position to unblock SIGWINCH for the `exec' case
> in exec.c, but couldn't find it yet. Maybe someone has a more specific
> idea than I do?
>
As far as I can tell, there are six calls to execve() in Src/exec.c. If a
winch_unblock() were placed just before each of those six calls, the
unblock in zfork() from that last patch could probably be reverted.
next prev parent reply other threads:[~2013-05-05 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <klbmnc$ieh$1@ger.gmane.org>
[not found] ` <130425111646.ZM17258@torch.brasslantern.com>
[not found] ` <klc0n1$34u$1@ger.gmane.org>
2013-04-26 0:53 ` Bart Schaefer
[not found] ` <20130425193817.2f82b60c@pws-pc.ntlworld.com>
[not found] ` <130425151839.ZM17476@torch.brasslantern.com>
2013-04-26 8:42 ` Peter Stephenson
[not found] ` <klc2ah$jiv$1@ger.gmane.org>
[not found] ` <130426080805.ZM18619__18102.73175729$1366989065$gmane$org@torch.brasslantern.com>
2013-04-26 17:59 ` Yuri D'Elia
[not found] ` <130426080805.ZM18619@torch.brasslantern.com>
[not found] ` <517C0E09.4040505@users.sourceforge.net>
2013-04-27 22:31 ` Bart Schaefer
2013-04-28 15:30 ` Yuri D'Elia
2013-04-29 1:03 ` Bart Schaefer
2013-04-29 1:59 ` Bart Schaefer
2013-05-05 0:01 ` Frank Terbeck
2013-05-05 6:52 ` Bart Schaefer
2013-05-05 9:38 ` Frank Terbeck
2013-05-05 17:53 ` Bart Schaefer [this message]
2013-05-05 18:37 ` Frank Terbeck
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=7Zdkq0St4cjCaFuEUmqYSTXjunSA=e_cx92gDCM9Y5L3g@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).