From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] TYPESET_TO_UNSET + misc.
Date: Wed, 21 Apr 2021 21:36:52 +0000 [thread overview]
Message-ID: <20210421213652.GF21343@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7aN4ZvT2pyPdoUN1GgTsSwsathLBVVq0N8fB9bb=d9Lng@mail.gmail.com>
Bart Schaefer wrote on Tue, Apr 20, 2021 at 17:06:10 -0700:
> On Tue, Apr 20, 2021 at 3:01 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >
> > The typesettounset branch is also relevant; it has been merged into
> > declarednull.
>
> Yes, but I committed to master branch by applying the patch, not by
> git wrangling.
Sure, but that pointer to that branch might still be useful to future
archaeologists, who'll find this thread by following the X-Seq in the
logs.
> > Worth an entry in NEWS?
>
> Probably. Pardon any gmail line wrapping below.
>
> Is it worth attempting to explain that
>
> setopt no_typesettounset
> source =(
> setopt typesettounset
> typeset something
> typeset -p something
> )
>
> does NOT re-create "something" as an unset variable?
I suppose this is somewhat implied by the fact that there's no «typeset»
syntax to create an unset variable when no_typesettounset is in effect?
> diff --git a/NEWS b/NEWS
> index cf270ff51..ee97868f9 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -35,6 +35,12 @@ widgets. This corresponds to long-standing
> behavior of other user ZLE
> widgets. Use the _complete_debug widget to capture XTRACE output, or
> use "functions -T" to enable tracing of specific completion functions.
>
> +With the new TYPESET_TO_UNSET option set, "typeset foo" leaves foo unset,
> +in contrast to the default behavior which assigns foo="". Any parameter
> +attributes such as numeric type, sorting, and padding are retained until
> +the parameter is explicitly unset or a conflicting value is assigned.
> +This is similar to default behavior of bash and ksh.
> +
> Changes from 5.7.1-test-3 to 5.8
> --------------------------------
>
next prev parent reply other threads:[~2021-04-21 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 5:52 Bart Schaefer
2021-04-16 6:44 ` Stephane Chazelas
2021-04-16 6:53 ` Stephane Chazelas
2021-04-18 21:03 ` Bart Schaefer
2021-04-20 22:01 ` Daniel Shahaf
2021-04-21 0:06 ` Bart Schaefer
2021-04-21 21:36 ` Daniel Shahaf [this message]
2021-04-21 22:07 ` 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=20210421213652.GF21343@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).