From: Bart Schaefer <schaefer@brasslantern.com>
To: Zaidhaan Hussain <zaidhaan@gmx.com>
Cc: zsh-workers@zsh.org
Subject: Re: Should (z) PE flag split & during expansion?
Date: Mon, 5 Jun 2023 13:01:21 -0700 [thread overview]
Message-ID: <CAH+w=7bWJQRJG46ayZ_6FaN5TW+cSv2=30uJk9xDv6BZHZRTYA@mail.gmail.com> (raw)
In-Reply-To: <rfqgtwa77p6aklvn6y4pcx2zu4jwmkd7f4cw44ygmtzj55izi6@au6wtpuvowe6>
On Fri, Jun 2, 2023 at 11:00 PM Zaidhaan Hussain <zaidhaan@gmx.com> wrote:
>
> printf '<%s>' ${(z)${:-'!-2:&'}}
> <!-2:><&>
>
> Which does not make sense if we consider that & is valid in parameter
> expansions.
History references are entirely separate from shell syntax -- they are
an interactive-use-only feature vaguely similar to macro expansion.
The (z) flag doesn't account for them at all, and really cannot.
prev parent reply other threads:[~2023-06-05 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 6:00 Zaidhaan Hussain
2023-06-05 20:01 ` Bart Schaefer [this message]
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=7bWJQRJG46ayZ_6FaN5TW+cSv2=30uJk9xDv6BZHZRTYA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zaidhaan@gmx.com \
--cc=zsh-workers@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).