From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: zmv exits from function
Date: Sun, 31 Dec 2023 13:44:03 -0800 [thread overview]
Message-ID: <CAH+w=7ZmVxsUJKXXPU7CUuSbPuDMzyX2rPrXEpuGGC8q-TH_bw@mail.gmail.com> (raw)
In-Reply-To: <707f3c88-b222-45b8-9512-30830ec02a88@eastlink.ca>
On Sun, Dec 31, 2023 at 7:53 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> So that's multi-pass parsing.
Again, no. It's only parsed once, into an internal format
(essentially, the same format used for "zcompile" files) and then
executed if syntactically correct. The only way to get another parse
is to use "eval".
Expansion and word splitting on can occur during execution, but that
doesn't change the syntax tree. Parsing does happen inside command
substitution but is limited to that syntactic scope.
next prev parent reply other threads:[~2023-12-31 21:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 17:42 Ray Andrews
2023-12-30 20:38 ` Bart Schaefer
2023-12-30 21:02 ` Ray Andrews
2023-12-30 22:21 ` Bart Schaefer
2023-12-30 21:15 ` Mikael Magnusson
2023-12-31 3:43 ` Ray Andrews
2023-12-31 3:58 ` Bart Schaefer
2023-12-31 15:53 ` Ray Andrews
2023-12-31 21:44 ` Bart Schaefer [this message]
2023-12-31 22:06 ` Ray Andrews
2024-01-02 14:51 ` Mark J. Reed
2024-01-02 17:01 ` Ray Andrews
2024-01-02 11:50 ` Peter Stephenson
2024-01-02 17:08 ` Ray Andrews
2024-01-02 17:47 ` Mark J. Reed
2024-01-02 18:16 ` Ray Andrews
2024-01-02 20:24 ` Bart Schaefer
2024-01-02 21:32 ` Ray Andrews
2024-01-02 17:48 ` Peter Stephenson
2024-01-02 19:07 ` Bart Schaefer
2024-01-02 19:52 ` Ray Andrews
2024-01-03 9:55 ` Peter Stephenson
2024-01-03 15:46 ` Ray Andrews
2024-01-03 19:01 ` Bart Schaefer
2023-12-30 22:34 ` Bart Schaefer
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=7ZmVxsUJKXXPU7CUuSbPuDMzyX2rPrXEpuGGC8q-TH_bw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).