From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] 'exec' runs shell functions and builtins
Date: Fri, 28 Jul 2017 10:58:59 -0700 [thread overview]
Message-ID: <CAH+w=7bE=MP0TqAeyPWP4Ut-UBXRDbVt2+DEnNb35BotA4BeYw@mail.gmail.com> (raw)
In-Reply-To: <20170727100206.4dda10d9@pwslap01u.europe.root.pri>
On Thu, Jul 27, 2017 at 2:02 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> % (setopt posixbuiltins; exec command echo foo)
> zsh: command not found: command
Chet Ramey emailed me:
=====
"However, all of the standard utilities, including the regular built-ins in
the table, but not the special built-ins described in Special Built-In
Utilities, shall be implemented in a manner so that they can be accessed
via the exec family of functions as defined in the System Interfaces volume
of POSIX.1-2008 and can be invoked directly by those standard utilities
that require it (env, find, nice, nohup, time, xargs)."
`command' is explicitly listed in the table in
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap01.html#tag_17_06
=====
So "exec command ..." is actually supposed to work, as is "exec read",
"exec getopts", etc. Urk.
next prev parent reply other threads:[~2017-07-28 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170725221050epcas4p131de822f47289e279c7de12de0d6c127@epcas4p1.samsung.com>
2017-07-25 21:49 ` Martijn Dekker
2017-07-26 9:23 ` Peter Stephenson
2017-07-26 9:27 ` Peter Stephenson
2017-07-26 12:53 ` Peter Stephenson
2017-08-04 15:34 ` Stephane Chazelas
2017-07-26 17:46 ` Bart Schaefer
2017-07-26 17:48 ` Bart Schaefer
2017-07-27 9:02 ` Peter Stephenson
2017-07-28 17:58 ` Bart Schaefer [this message]
2017-08-11 15:10 ` Kamil Dudka
2017-08-11 15:25 ` Peter Stephenson
2017-08-14 7:19 ` Kamil Dudka
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=7bE=MP0TqAeyPWP4Ut-UBXRDbVt2+DEnNb35BotA4BeYw@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).