From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Michael Smith <michael.smith@cloudera.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug: 'export FOO' not idempotent
Date: Mon, 27 Jun 2022 23:50:29 +0200 [thread overview]
Message-ID: <CAN=4vMqAqyzZhXjMQpnRSUpki+VTc+tQKptP3jQYm3Aoj1zfww@mail.gmail.com> (raw)
In-Reply-To: <3accd9cb-aede-41ce-96e6-f3e175392b9d@www.fastmail.com>
On Mon, Jun 27, 2022 at 11:44 PM Lawrence Velázquez <larryv@zsh.org> wrote:
> https://www.zsh.org/mla/workers/2020/msg01350.html
>
> It was resolved in zsh 5.9 with the introduction of the TYPESET_TO_UNSET
> option, but as per workers/47545, "[t]his is a long standing feature
> of zsh, so the default behaviour is not going to change."
>
> https://www.zsh.org/mla/workers/2020/msg01364.html
It's odd that `export FOO` doesn't have the same effect as `repeat 2
export FOO` when TYPESET_TO_UNSET is not in effect. Would it make more
sense for the first command to have the same effect as the second?
Another oddity that suggests the same resolution:
% export FOO
% typeset -p FOO
% export FOO=''
% env | grep FOO
%
Either `export FOO` is doing something weird or `typeset p FOO` is lying.
Roman.
prev parent reply other threads:[~2022-06-27 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 21:11 Michael Smith
2022-06-27 21:43 ` Lawrence Velázquez
2022-06-27 21:46 ` Michael Smith
2022-06-27 21:52 ` Lawrence Velázquez
2022-06-27 21:58 ` Roman Perepelitsa
2022-06-27 22:37 ` Lawrence Velázquez
2022-07-02 22:05 ` Bart Schaefer
2022-07-02 22:14 ` Bart Schaefer
2022-06-27 21:50 ` Roman Perepelitsa [this message]
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='CAN=4vMqAqyzZhXjMQpnRSUpki+VTc+tQKptP3jQYm3Aoj1zfww@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=larryv@zsh.org \
--cc=michael.smith@cloudera.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).