From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: "typeset -p" inconsistency
Date: Wed, 2 Nov 2022 10:19:04 -0700 [thread overview]
Message-ID: <10c0411d-60a3-2dcc-0664-18eb9d40b23f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7afwFmEToJvV4uGehOnJwD8Jvai2o41ZwLqmA6ZOzFAdw@mail.gmail.com>
On 2022-11-02 10:04, Bart Schaefer wrote:
>
> Of course it does.
>
> % set | grep -wi path
> PATH=/opt/local/bin:/opt/local/sbin:/Users/schaefer/bin:/usr/local/bin:/usr/bin:/bin:/sbin:/usr/sbin:/usr/X11/bin:/Library/PostgreSQL/8.3/bin:/Developer/usr/bin
> path=( /opt/local/bin /opt/local/sbin /Users/schaefer/bin
> /usr/local/bin /usr/bin /bin /sbin /usr/sbin /usr/X11/bin
> /Library/PostgreSQL/8.3/bin /Developer/usr/bin )
>
Different tho, they have different cases and there is that '-T' issue
which is a complication perhaps better left as it is. Only typeset
gives us that '-g -aT' duplication. Mind, typeset does deal with that
elegantly:
2 /aWorking/Zsh/Source/Wk 0 $ typeset -mp "(#i)path"
typeset -aT PATH path=( . /aWorking/Zsh/System /aWorking/Bin
/usr/local/bin /usr/sbin /usr/bin )
export -T PATH path=( . /aWorking/Zsh/System /aWorking/Bin
/usr/local/bin /usr/sbin /usr/bin )
... now that I understand it, I can see that 'PATH path' is just how it
needs to be displayed. But not twice please and of course you can add
the '-g' if from within a function. Nope, it's just not very friendly.
I'm right about this.
next prev parent reply other threads:[~2022-11-02 17:20 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
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 [this message]
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=10c0411d-60a3-2dcc-0664-18eb9d40b23f@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).