From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: uninvited members of associative array
Date: Fri, 16 Dec 2022 16:30:14 +0000 [thread overview]
Message-ID: <09d09690-08c8-4499-9011-9c45d7676f52@app.fastmail.com> (raw)
In-Reply-To: <902fb047-3435-89a3-e7ea-74e74075c2c6@eastlink.ca>
Ray Andrews wrote on Fri, 16 Dec 2022 14:13 +00:00:
> ... this is exactly the sort of thing I was talking to Lawrence about --
> not really a hard error, just some printout issue. I'll pursue that. I
> (think I) understand that AAs are very fragile creatures and as you
> demonstrate, easily confused. I'll bag it.
I think the better takeaway here is that the "default" (barest) syntax
isn't always the right one. There's any number of examples of this:
- Variable expansions, «${foo}». Scalars need to be quoted; arrays need
to be quoted and @'d; assocs need to be quoted, @'d, and (kv)'d. The
actual meaning of unquoted «${foo}» — expand to all non-null values —
isn't commonly needed.
- «ls *.txt» without a «--» guard.
- «print -- $foo» without «-r».
next prev parent reply other threads:[~2022-12-16 16:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 23:48 Ray Andrews
2022-12-16 0:05 ` Lawrence Velázquez
2022-12-16 0:48 ` Ray Andrews
2022-12-16 1:29 ` Lawrence Velázquez
2022-12-16 2:09 ` Dominik Vogt
2022-12-16 2:56 ` Ray Andrews
2022-12-16 3:21 ` Lawrence Velázquez
2022-12-16 4:16 ` Ray Andrews
2022-12-16 10:05 ` Dominik Vogt
2022-12-16 14:13 ` Ray Andrews
2022-12-16 15:19 ` Dominik Vogt
2022-12-16 19:14 ` Ray Andrews
2022-12-16 16:30 ` Daniel Shahaf [this message]
2022-12-16 18:21 ` Ray Andrews
2022-12-16 19:04 ` Dominik Vogt
2022-12-16 20:10 ` Ray Andrews
2022-12-16 21:15 ` Dominik Vogt
2022-12-16 21:33 ` Bart Schaefer
2022-12-16 21:59 ` Dominik Vogt
2022-12-16 22:15 ` Bart Schaefer
2022-12-16 23:33 ` Ray Andrews
2022-12-17 12:47 ` Pier Paolo Grassi
2022-12-17 17:32 ` Ray Andrews
2022-12-17 18:10 ` Ray Andrews
2022-12-17 18:19 ` Roman Perepelitsa
2022-12-17 20:31 ` Ray Andrews
2022-12-17 20:49 ` Bart Schaefer
2022-12-17 21:07 ` Lawrence Velázquez
2022-12-17 21:52 ` Ray Andrews
2022-12-17 22:10 ` Bart Schaefer
2022-12-17 23:41 ` Daniel Shahaf
2022-12-18 0:15 ` Ray Andrews
2022-12-18 0:25 ` Daniel Shahaf
2022-12-18 2:13 ` Ray Andrews
2022-12-18 20:12 ` Daniel Shahaf
2022-12-18 20:26 ` Bart Schaefer
2022-12-18 20:41 ` Ray Andrews
2022-12-18 3:44 ` Lawrence Velázquez
2022-12-17 23:25 ` Daniel Shahaf
2022-12-16 21:33 ` Ray Andrews
2022-12-16 20:25 ` Daniel Shahaf
2022-12-16 21:43 ` Dominik Vogt
2022-12-16 3:20 ` Bart Schaefer
2022-12-16 4:15 ` Ray Andrews
2022-12-16 8:12 ` Roman Perepelitsa
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=09d09690-08c8-4499-9011-9c45d7676f52@app.fastmail.com \
--to=d.s@daniel.shahaf.name \
--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).