From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: "typeset -p" inconsistency
Date: Wed, 2 Nov 2022 05:56:23 -0700 [thread overview]
Message-ID: <446c90ae-6aea-8a7e-ea3a-a0a47f79a846@eastlink.ca> (raw)
In-Reply-To: <7e4f0447-694a-4971-9b23-77b323574f11@app.fastmail.com>
On 2022-11-01 20:11, Lawrence Velázquez wrote:
> As Bart already explained, it is not "one and the same variable"
> -- PATH and path are *two separate variables*. So there is no
> "duplication".
This country boy sees them as duplication. 'set' does not print them
twice. Anyway you guys are happy with it so I'm flogging a dead horse
as usual. Besides it's easy enough to filter out Tweedle-Dee and leave
Tweedle-Dum cuz I learn nothing from the one that I don't already know
from the other. I know I'm fanatical about this sort of thing.
> (I suppose one could argue that "-g" should always be output for
> global variables, even outside of functions, for the sake of
> consistency.)
Consistency is one of my cardinal virtues, I like it alot. The
Linux/Unix world doesn't mind a bit of fuzz tho.
> (As an aside, "test" is a builtin and POSIX-mandated utility, so
> using that name for your own purposes is not the best idea.)
It's the sort of thing you learn via hard knocks.
next prev parent reply other threads:[~2022-11-02 12:57 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 [this message]
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=446c90ae-6aea-8a7e-ea3a-a0a47f79a846@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).