From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: 'emulate sh -c' and $0
Date: Tue, 3 Jun 2014 14:21:01 -0700 [thread overview]
Message-ID: <CAH+w=7ZRU-M03rc4_kLNE3rSJXHyM4YBWenwHmFNg5gt8DZ5+w@mail.gmail.com> (raw)
In-Reply-To: <538E2CDD.7070106@bbn.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Jun 3, 2014 1:15 PM, "Richard Hansen" <rhansen@bbn.com> wrote:
>
> Wow, thank you for committing this change to master! It works well in
> my limited testing, except for the documented limitation that
> POSIX_ARGZERO stays enabled when calling a non-emulated function from a
> function defined in 'emulate <shell> -c'. I'm not sure how much this
> will matter in practice, but if backward compatibility wasn't a concern
> it'd be nice if zsh temporarily restored options when invoking a
> function outside the 'emulate <shell> -c' boundary.
What this is effectively requesting is that all functions have "sticky"
options, always. We already rejected that idea for reasons of dynamic
scoping when originally designing "emulate ... -c". I suppose a special
case could be made of POSIX_ARGZERO such that it is always sticky even when
other options are not, but that seems like an awful lot of effort for
something that doesn't matter most of the time.
next prev parent reply other threads:[~2014-06-03 21:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 23:04 Richard Hansen
2014-05-30 3:45 ` Bart Schaefer
2014-05-30 8:49 ` Richard Hansen
2014-05-30 17:00 ` Bart Schaefer
2014-05-30 21:14 ` Richard Hansen
2014-05-31 5:13 ` Bart Schaefer
2014-05-31 23:47 ` Bart Schaefer
2014-06-03 20:15 ` Richard Hansen
2014-06-03 20:26 ` Peter Stephenson
2014-06-03 21:10 ` Bart Schaefer
2014-06-03 23:35 ` Richard Hansen
2014-06-04 0:09 ` Bart Schaefer
2014-06-03 21:21 ` Bart Schaefer [this message]
2014-06-03 22:54 ` Richard Hansen
2014-06-04 0:03 ` Bart Schaefer
2014-06-04 1:10 ` Bart Schaefer
2014-06-04 1:23 ` Bart Schaefer
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=7ZRU-M03rc4_kLNE3rSJXHyM4YBWenwHmFNg5gt8DZ5+w@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).