From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
Zsh hackers list <zsh-workers@zsh.org>,
Stephane Chazelas <stephane@chazelas.org>
Subject: Re: More rabbit-holes with unset variables
Date: Wed, 25 Nov 2020 16:17:46 -0600 [thread overview]
Message-ID: <CAMP44s0-ki=TBzTwnqx10FcTLX4mbphwN88UCx0+h97JTecBWA@mail.gmail.com> (raw)
In-Reply-To: <20201125131921.vay7h3xk5qn4odgg@chazelas.org>
On Wed, Nov 25, 2020 at 7:19 AM Stephane Chazelas <stephane@chazelas.org> wrote:
>
> 2020-11-24 23:02:05 -0800, Bart Schaefer:
> > I was experimenting with ksh to look deeper into adding behavior to
> > ksh_typeset in zsh, and discovered that this example:
> [...]
>
> Sorry I didn't read the full discussion as I just subscribed to
> the list, but I did have a look at the differences between local
> scope implementations at some point and there are many many
> variations between shells.
>
> I did find zsh was far from being the worst one there.
Yes, but the discussion was about inheritance and the behavior of
unset, not about what we are discussing here.
They did mention the zsh behavior, but that's that's it. I don't think
anyone contested what in my opinion is the natural behavior, which is
described initially in the description:
The variable whose name is specified shall be created as a local
variable with name "name". It
shall inherit its initial value, as well as the exported and
readonly flags, from the variable
with the same name in the surrounding dynamic scope if there is one;
otherwise, the variable is
initially unset. Then, if "=word" is provided, the value of that
local variable shall then be set
to word.
So, the variable is initially unset, *unless* "=word" is provided.
Do you think anyone objected to that behavior?
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2020-11-25 22:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 7:02 Bart Schaefer
2020-11-25 13:19 ` Stephane Chazelas
2020-11-25 22:17 ` Felipe Contreras [this message]
2020-11-26 6:10 ` Stephane Chazelas
2020-11-26 7:20 ` Felipe Contreras
2020-11-26 11:21 ` Oliver Kiddle
2020-11-26 11:29 ` Roman Perepelitsa
2020-11-26 19:08 ` Felipe Contreras
2020-11-26 19:29 ` Felipe Contreras
2020-11-26 21:13 ` Bart Schaefer
2020-11-26 21:31 ` Felipe Contreras
2020-11-26 23:29 ` Bart Schaefer
2020-11-26 23:32 ` Bart Schaefer
2020-11-26 23:53 ` Felipe Contreras
2020-11-27 0:23 ` Bart Schaefer
2020-11-27 1:51 ` Felipe Contreras
2020-11-27 20:01 ` Bart Schaefer
2020-11-27 21:49 ` Felipe Contreras
2020-11-27 22:06 ` Bart Schaefer
2020-11-27 23:35 ` Felipe Contreras
2020-11-26 22:07 ` Bart Schaefer
2020-11-26 20:41 ` Bart Schaefer
2020-11-26 20:49 ` Stephane Chazelas
2020-11-26 21:20 ` Felipe Contreras
2020-11-26 22:41 ` Bart Schaefer
2020-11-26 23:45 ` Felipe Contreras
2020-11-27 0:09 ` Bart Schaefer
2020-11-27 0:30 ` Felipe Contreras
2020-11-27 0:51 ` Bart Schaefer
2020-11-27 1:30 ` Felipe Contreras
2020-11-27 20:54 ` Bart Schaefer
2020-11-27 22:10 ` Felipe Contreras
2020-11-27 22:39 ` Bart Schaefer
2020-11-28 0:00 ` Felipe Contreras
2020-11-28 0:04 ` Bart Schaefer
2020-11-28 10:52 ` Felipe Contreras
2020-11-28 0:36 ` The emulation rabbit-hole RE typeset/unset Bart Schaefer
2020-11-28 11:35 ` Felipe Contreras
2020-11-28 16:56 ` Bart Schaefer
2020-12-01 8:49 ` Felipe Contreras
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='CAMP44s0-ki=TBzTwnqx10FcTLX4mbphwN88UCx0+h97JTecBWA@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=stephane@chazelas.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).