From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: "typeset -p" inconsistency
Date: Tue, 1 Nov 2022 12:07:32 +0000 (GMT) [thread overview]
Message-ID: <1742037247.4104297.1667304452985@mail.virginmedia.com> (raw)
In-Reply-To: <CAH+w=7bjk4cS7N3P5t2YK3LLkV_4ZcZgV8sAmSP4Y2=UiNXPSg@mail.gmail.com>
> On 01/11/2022 05:00 Bart Schaefer <schaefer@brasslantern.com> wrote:
> % setopt extendedglob
> % typeset -U CDPATH
> % typeset -mp '(#i)cdpath'
> typeset -aT CDPATH cdpath=( )
> typeset -UT CDPATH cdpath=( )
>
> Note the -U attribute is only retained when printing the assignment
> for the scalar ... which is literally correct, since it was only
> asserted for the scalar, but lossy, whereas the array-ness is
> preserved in both cases (as long as typeset remains a reserved word).
That does correctly reflect the behaviour of the -U flag, however.
% typeset -T FOO foo
% foo=(one two three)
% typeset -U foo
% print $foo
one two three
% foo+=(two) # flag applied
% print $foo
one two three
% FOO+=:two # flag not applied
% print $foo
one two three two
Other consequences of this are logical, e.g. "foo=($foo)" does
prune, "typeset -U FOO" works as expected.
The ideal output for typeset -p to reflect how this works might
be to output the typeset -T separately from any indication
of any flags set on one or other of the two interfaces to the
value, i.e. something like what I typed (but with the current
value somewhere).
typeset -T FOO foo=(one two three)
typeset -U foo
pws
next prev parent reply other threads:[~2022-11-01 12:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:21 var=$( typeset "$1" ) ... not within a function Ray Andrews
2022-10-20 17:25 ` Roman Perepelitsa
2022-10-20 17:51 ` Ray Andrews
2022-10-20 17:54 ` Roman Perepelitsa
2022-10-20 18:38 ` Ray Andrews
2022-10-20 18:44 ` Roman Perepelitsa
2022-10-20 19:15 ` Ray Andrews
2022-10-20 19:35 ` Roman Perepelitsa
2022-10-20 20:48 ` Ray Andrews
2022-10-21 0:54 ` Bart Schaefer
2022-10-21 1:58 ` Ray Andrews
2022-10-21 2:25 ` Bart Schaefer
2022-10-21 14:24 ` Ray Andrews
2022-10-21 14:37 ` Ray Andrews
2022-10-21 17:34 ` Roman Perepelitsa
2022-11-01 5:00 ` "typeset -p" inconsistency Bart Schaefer
2022-11-01 12:07 ` Peter Stephenson [this message]
2022-11-01 12:40 ` Ray Andrews
2022-11-01 19:08 ` Bart Schaefer
2022-11-01 21:25 ` Ray Andrews
2022-11-01 21:40 ` Bart Schaefer
2022-11-01 22:46 ` Ray Andrews
2022-11-02 1:13 ` Lawrence Velázquez
2022-11-02 2:42 ` Ray Andrews
2022-11-02 3:11 ` Lawrence Velázquez
2022-11-02 12:56 ` Ray Andrews
2022-11-02 17:04 ` Bart Schaefer
2022-11-02 17:19 ` Ray Andrews
2022-11-02 18:21 ` Bart Schaefer
2022-11-02 3:10 ` Bart Schaefer
2022-11-02 17:09 ` Ray Andrews
2022-10-20 17:29 ` var=$( typeset "$1" ) ... not within a function Mikael Magnusson
2022-10-20 17:43 ` Ray Andrews
2022-10-21 17:33 ` Ray Andrews
2022-10-21 18:25 ` Bart Schaefer
2022-10-21 18:57 ` Ray Andrews
2022-10-21 19:02 ` Roman Perepelitsa
2022-10-21 19:06 ` Ray Andrews
2022-10-21 19:04 ` Ray Andrews
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=1742037247.4104297.1667304452985@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-users@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).