From: Jett Husher <jetthusher@pm.me>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: Question on unintuitive behaviour for function execution and parameter assignment
Date: Wed, 13 Oct 2021 08:42:43 +0000 [thread overview]
Message-ID: <6uviEgEHuYei0UyfGfR_mqJvrNcXyJ5zfUwrQViRtmWwGeZwRR1C26lsUK9_D-V_GzCg5cG2gQ2IwHxScwLySDcy71rAa2RMpK5XF8BvtkE=@pm.me> (raw)
In-Reply-To: <917132892.507659.1634027485386@mail2.virginmedia.com>
On Tuesday, October 12th, 2021 at 10:31, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> This is covered by the POSIX_BUILTINS option. Generally, the POSIX_* options are
>
> the place to look for this sort of think --- granted that can be a bit of hunt.
I wouldn't even think to look at POSIX_* variables because POSIX-2017
explicitly tells that it's unspecified "Whether or not the variable assignments persist after
the completion of the function", so, naturally, I though that this behaviour was compliant.
> Usually an easy test to see if zsh does have the POSIX behaviour available is
>
> to start a new shell as
>
> ARGV0=sh zsh
>
> and see what behaviour that gives you. That should be maximally compatible,
>
> although it doesn't help you find which option controls the behaviour.
I would keep that in mind next time. I used to compare the executions in bash, since I thought
it's more compliant, but I guess it's not the best option since GNU also states that it
takes the standards as a recommendation and not a rule.
I still believe this needs to be mentioned in FUNCTIONS or SIMPLE COMMANDS & PIPELINES of zshmisc(1).
Or zshparam(1) perhaps? I would love to suggest my help with updating man pages but I'm not sure
if you accept commits the side. Or even how the development is done around here :shrug:
Either way, a world of thanks for the help, Peter.
- Jett
next prev parent reply other threads:[~2021-10-13 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 8:20 Jett Husher
2021-10-12 8:31 ` Peter Stephenson
2021-10-13 8:42 ` Jett Husher [this message]
2021-10-13 9:10 ` 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='6uviEgEHuYei0UyfGfR_mqJvrNcXyJ5zfUwrQViRtmWwGeZwRR1C26lsUK9_D-V_GzCg5cG2gQ2IwHxScwLySDcy71rAa2RMpK5XF8BvtkE=@pm.me' \
--to=jetthusher@pm.me \
--cc=p.w.stephenson@ntlworld.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).