Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Nofork ${{var}...} edge cases

X-seq: zsh-workers 52839
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: Re: Nofork ${{var}...} edge cases
Date: Wed, 27 Mar 2024 18:21:43 -0700
Archived-at: <https://zsh.org/workers/52839>
In-reply-to: <CAH+w=7Y7gD8vKsk-=UEaf4N0j9u+ruNKS8nUZGZNAb23cRGSEQ@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <CAH+w=7YHZspc2JVBxkkYO69Cr9x__s-m4UQqRUfOetZYssUqnw@mail.gmail.com> <42966-1711578160.323146@w_2U.aZv1.yyMw> <CAH+w=7Y7gD8vKsk-=UEaf4N0j9u+ruNKS8nUZGZNAb23cRGSEQ@mail.gmail.com>

On Wed, Mar 27, 2024 at 6:00 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> On Wed, Mar 27, 2024 at 3:22 PM Oliver Kiddle <opk@xxxxxxx> wrote:
> >
> > > Or we could declare ${{REPLY}...} as NOT synonymous with ${|...} and
> > > localize REPLY only in the latter of those.  That might actually make
> > > more sense.
>
> Hrm, unfortunately that gets a bit dicey, because ${ ... } relies on
> having the magic local $REPLY as a place to stash the captured stdout

Oh, no, it doesn't:  I confused myself because some the tests in D10 do so.

Follow-Ups:
- Re: Nofork ${{var}...} edge cases
  - From: Bart Schaefer

References:
- Nofork ${{var}...} edge cases
  - From: Bart Schaefer
- Re: Nofork ${{var}...} edge cases
  - From: Oliver Kiddle
- Re: Nofork ${{var}...} edge cases
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author