From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: [BUG] exec + builtin and traps
Date: Tue, 12 Sep 2017 13:42:20 +0200 [thread overview]
Message-ID: <20170912114220.GB1794@zira.vinc17.org> (raw)
In-Reply-To: <20170912115006.4d1b964d@pwslap01u.europe.root.pri>
On 2017-09-12 11:50:06 +0100, Peter Stephenson wrote:
> On Tue, 12 Sep 2017 12:39:19 +0200
> Vincent Lefevre <vincent@vinc17.net> wrote:
> > No, by default (with TRAPS_ASYNC unset), traps are run *after* the
> > child process has exited:
>
> True, but the *builtin* is an eval list, that only terminates when it
> has executed an arbitrary set of other commands. The trap is executed
> at the end of this list, before control returns back to eval. We are
> not exec'ing sleep here, we are exec'ing eval, so there is time after
> the *child* process is executed, as in the TRAPS_ASYNC doc you quote.
>
> eval, unlike exec, is not an permanent handoff of control to the
> following command.
OK, this was a bit confusing from the description of "eval" by POSIX,
which describes it as a way to construct a command:
The eval utility shall construct a command by concatenating
arguments together, separating each with a <space> character.
The constructed command shall be read and executed by the shell.
BTW, the way zsh handles "eval" is still strange:
----------------------------------------
trap 'echo foo' USR1
( sleep 1; kill -USR1 $$; ) &
eval "wait && echo bar"
echo OK
----------------------------------------
outputs
foo
bar
OK
----------------------------------------
trap 'echo foo' USR1
( sleep 1; kill -USR1 $$; ) &
wait && echo bar
echo OK
----------------------------------------
outputs
foo
OK
All the other shells output
foo
OK
in both cases.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2017-09-12 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170912101045epcas2p4cae7e7df78ef035900f9c6099dc054fb@epcas2p4.samsung.com>
2017-09-12 10:02 ` Vincent Lefevre
2017-09-12 10:19 ` Peter Stephenson
2017-09-12 10:39 ` Vincent Lefevre
2017-09-12 10:50 ` Peter Stephenson
2017-09-12 11:42 ` Vincent Lefevre [this message]
2017-09-12 11:51 ` Peter Stephenson
2017-09-12 12:02 ` Vincent Lefevre
2017-09-12 12:10 ` Peter Stephenson
2017-09-12 14:21 ` trap, eval and wait (was: [BUG] exec + builtin and traps) Vincent Lefevre
2017-09-12 15:04 ` Peter Stephenson
2017-09-13 9:55 ` Peter Stephenson
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=20170912114220.GB1794@zira.vinc17.org \
--to=vincent@vinc17.net \
--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).