Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
The (e) parameter flag and side-effects
- X-seq: zsh-workers 51546
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: The (e) parameter flag and side-effects
- Date: Thu, 9 Mar 2023 15:54:05 -0800
- Archived-at: <https://zsh.org/workers/51546>
- In-reply-to: <22530-1678390068.958410@dJKq.2wyk.2KSv>
- List-id: <zsh-workers.zsh.org>
- References: <20230309123303.77hztdd63lvxafg4@eliaspc> <22530-1678390068.958410@dJKq.2wyk.2KSv>
On Thu, Mar 9, 2023 at 11:28 AM Oliver Kiddle <opk@xxxxxxx> wrote:
>
> While using (e) is arguably the right thing to do, it will expand things
> like command-substitution and we've always intentionally shied away
> from expanding anything that could have side-effects when parsing the
> command-line for completion.
We could add a flag for that, though, I think; it would just need to
do the same trick I applied to subscript values in named references,
that is, toggle the EXECOPT flag off and back on around (or in) the
call to subst_parse_str().
Messages sorted by:
Reverse Date,
Date,
Thread,
Author