From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: "typeset -p" inconsistency
Date: Mon, 31 Oct 2022 22:00:18 -0700 [thread overview]
Message-ID: <CAH+w=7bjk4cS7N3P5t2YK3LLkV_4ZcZgV8sAmSP4Y2=UiNXPSg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bekYoZn4QDgBvtfXnJvVKQjTtCjO-QuRsURN+seM5PPA@mail.gmail.com>
On Thu, Oct 20, 2022 at 7:25 PM, I wrote:
>
> > typeset -T CDPATH cdpath=( )
> > typeset -aT CDPATH cdpath=( )
>
> The first one is the (incorrect) assignment for $CDPATH.
Nobody called me out on that ... the first assignment is actually just
fine. I'm not sure how I ended up thinking that didn't work. There
is, however, a related buglet:
% 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).
next prev parent reply other threads:[~2022-11-01 5:01 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 ` Bart Schaefer [this message]
2022-11-01 12:07 ` "typeset -p" inconsistency Peter Stephenson
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='CAH+w=7bjk4cS7N3P5t2YK3LLkV_4ZcZgV8sAmSP4Y2=UiNXPSg@mail.gmail.com' \
--to=schaefer@brasslantern.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).