From: Yuri D'Elia <wavexx@users.sourceforge.net>
To: zsh-workers@zsh.org
Cc: zsh-users@zsh.org
Subject: Re: precmd: write error: interrupted
Date: Fri, 26 Apr 2013 19:59:19 +0200 [thread overview]
Message-ID: <517AC077.9080703@users.sourceforge.net> (raw)
In-Reply-To: <130426080805.ZM18619__18102.73175729$1366989065$gmane$org@torch.brasslantern.com>
On 04/26/2013 05:08 PM, Bart Schaefer wrote:
> } What other syscalls would be interrupted by SIGWINCH that shouldn't be
> } restarted? Right now I cannot think of anything that SIGWINCH should
> } interrupt.
>
> I've been thinking about this, and the problem with using SA_RESTART is
> twofold:
>
> (1) [Minor] Some platforms don't have restartable syscalls, so this won't
> work everywhere. But perhaps the intersection of non-restarable syscalls
> and support for SIGWINCH is empty.
(I'm somehow curious of which systems don't support SIGWINCH, must be
particularly old).
> (2) [Potentially major] A user-defined trap can be installed for the
> SIGWINCH signal. That means arbitrary shell code might execute during
> handling of the signal, so all sorts of things might happen mid-write,
> not just the default ioctls.
I see, and now I also see your reasoning about queuing SIGWINCH
everywhere except when waiting in zleread. At any rate, that's the only
point where updating the terminal for the upcoming output makes sense.
Updating the column count (for example) while in the middle of a widget
expansion for instance won't likely help (or maybe even break some
invariant).
next prev parent reply other threads:[~2013-04-26 18:38 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 [this message]
[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
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=517AC077.9080703@users.sourceforge.net \
--to=wavexx@users.sourceforge.net \
--cc=zsh-users@zsh.org \
--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).