From: Christoph Anton Mitterer <calestyo@scientia.org>
To: Martijn Dekker <martijn@inlv.org>,
DASH shell mailing list <dash@vger.kernel.org>
Subject: Re: wrong behaviour when unsetting/setting some variables
Date: Thu, 29 Feb 2024 20:03:41 +0100 [thread overview]
Message-ID: <b83fbaba7b5d6d5935131febbcecb10fe9152628.camel@scientia.org> (raw)
In-Reply-To: <96806056-0aa2-467b-9460-71f142b71bad@inlv.org>
On Thu, 2024-02-29 at 17:58 +0000, Martijn Dekker wrote:
> No shell currently behaves like that, and it would make no sense, as
> 'unset'
> and 'empty value' are distinct states.
Well in the end I don't mind what's done, but would prefer that the
specs unambiguously describe it, and even if just says that the
behaviour is unspecified.
People read it, and by just reading the description of the export tool
one might conclude, that such variable is exported to the environment
of an executed command.
Cheers,
Chris.
next prev parent reply other threads:[~2024-02-29 20:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 2:07 wrong behaviour when unsetting/setting some variables Christoph Anton Mitterer
2024-02-27 3:07 ` Harald van Dijk
2024-02-27 3:28 ` Christoph Anton Mitterer
2024-02-27 10:24 ` Harald van Dijk
2024-02-27 4:23 ` Lawrence Velázquez
2024-02-27 5:11 ` Christoph Anton Mitterer
2024-02-27 7:53 ` Lawrence Velázquez
2024-02-29 12:29 ` Christoph Anton Mitterer
2024-02-29 17:58 ` Martijn Dekker
2024-02-29 19:03 ` Christoph Anton Mitterer [this message]
2024-02-28 0:56 ` Harald van Dijk
2024-02-29 12:24 ` Christoph Anton Mitterer
2024-02-29 18:03 ` Martijn Dekker
2024-02-29 17:41 ` Martijn Dekker
2024-02-29 18:07 ` Harald van Dijk
2024-02-29 18:45 ` Martijn Dekker
2024-02-29 18:56 ` Harald van Dijk
2024-03-10 21:33 ` Martijn Dekker
2024-04-11 1:26 ` Christoph Anton Mitterer
2024-04-11 7:43 ` [PATCH] var: Fix unexporting of local variables using unset Herbert Xu
2024-04-11 13:27 ` Christoph Anton Mitterer
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=b83fbaba7b5d6d5935131febbcecb10fe9152628.camel@scientia.org \
--to=calestyo@scientia.org \
--cc=dash@vger.kernel.org \
--cc=martijn@inlv.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox