From: "Lawrence Velázquez" <larryv@zsh.org>
To: zsh-users@zsh.org
Subject: Re: nesting issue
Date: Sun, 05 May 2024 15:44:35 -0400 [thread overview]
Message-ID: <9a82e3a2-0bf1-4563-b5ae-c40d9ef659c9@app.fastmail.com> (raw)
In-Reply-To: <cfcecae4-71d5-4542-8683-472138a3a491@eastlink.ca>
On Sun, May 5, 2024, at 9:13 AM, Ray Andrews wrote:
> On 2024-05-04 20:20, Bart Schaefer wrote:
>> They give "bad substitution" because you can't have a space before the
>> closing "}" / after the closing ")" in the parameter expansion.
>>
>> local sorted=( "${(f)$(print -l "${(n)in[@]}")}" )
>>
> Nuts, I wouldn't have even considered that.
>
> Even tho it is accepted here?:
>
> sorted=( "${(f)sorted}" )
You're not comparing the right spaces. The problem Bart pointed
out is more akin to
sorted=( "${(f)sorted }" )
> One thing tho, since nested quotes end up un-quoting the inner
> quotation (or is this an exception?)
Command substitution introduces a new quoting context. Things like
"$(cmd "arg with spaces")"
work fine.
> I'm thinking that:
>
> local sorted=( "${(f)$(print -l ${(n)in[@]})}" )
>
> ... one set of quotes -- should be fine. And it seems fine.
Unquoted ${(n)in[@]} drops empty elements and is equivalent to
unquoted ${(n)in}. Whether that's acceptable is dependent on
application requirements, as always.
--
vq
next prev parent reply other threads:[~2024-05-05 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 19:36 Ray Andrews
2024-05-05 3:20 ` Bart Schaefer
2024-05-05 5:39 ` Lawrence Velázquez
2024-05-05 5:40 ` Roman Perepelitsa
2024-05-05 13:52 ` Ray Andrews
2024-05-05 20:14 ` Lawrence Velázquez
2024-05-05 22:18 ` Ray Andrews
2024-05-05 23:26 ` Lawrence Velázquez
2024-05-06 1:51 ` Ray Andrews
2024-05-06 3:22 ` Bart Schaefer
2024-05-06 13:01 ` Ray Andrews
2024-05-06 3:43 ` Lawrence Velázquez
2024-05-06 13:09 ` Ray Andrews
2024-05-05 13:13 ` Ray Andrews
2024-05-05 19:44 ` Lawrence Velázquez [this message]
2024-05-05 20:14 ` Ray Andrews
2024-05-05 20:45 ` Lawrence Velázquez
2024-05-05 22:22 ` 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=9a82e3a2-0bf1-4563-b5ae-c40d9ef659c9@app.fastmail.com \
--to=larryv@zsh.org \
--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).