From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: permission denied
Date: Thu, 20 Apr 2023 20:12:22 -0700 [thread overview]
Message-ID: <CAH+w=7ZC1meWEbu7vLWbioC3y+00_aVXRN91TCNYk=eEoOY4Vg@mail.gmail.com> (raw)
In-Reply-To: <c9973485-704e-2573-150d-2b84b86a629c@eastlink.ca>
On Thu, Apr 20, 2023 at 3:47 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> Ah! '(z)' takes care not to split within quotes. Sheesh, why doesn't
> the manual just say that?
Because that's not all it does. The first part of the sentence --
"Split the result of the expansion into words using shell parsing" --
is the important bit. (The "i.e." in "i.e. taking" should probably be
an "e.g." as it is only one example of what happens.)
$=x only splits on spaces. (z) gives you a separate word for each
shell token, so e.g. "<file" becomes the two words "<" and "file", and
"echo foo;" becomes 3 words "echo", "foo", and ";", and so on.
next prev parent reply other threads:[~2023-04-21 3:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 18:34 Ray Andrews
2023-04-17 19:07 ` Roman Perepelitsa
2023-04-17 20:41 ` Ray Andrews
2023-04-17 21:52 ` Bart Schaefer
2023-04-17 22:44 ` Ray Andrews
2023-04-18 2:41 ` Bart Schaefer
2023-04-18 3:35 ` Ray Andrews
2023-04-20 21:35 ` Ray Andrews
2023-04-20 21:47 ` Roman Perepelitsa
2023-04-20 22:09 ` Ray Andrews
2023-04-20 22:13 ` Bart Schaefer
2023-04-20 22:47 ` Ray Andrews
2023-04-21 3:12 ` Bart Schaefer [this message]
2023-04-21 13:33 ` Ray Andrews
2023-04-21 14:12 ` Peter Stephenson
2023-04-21 14:42 ` Ray Andrews
2023-04-21 21:58 ` Bart Schaefer
2023-04-22 0:56 ` Ray Andrews
2023-04-20 22:17 ` Roman Perepelitsa
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 23:01 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=7ZC1meWEbu7vLWbioC3y+00_aVXRN91TCNYk=eEoOY4Vg@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).