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

Re: [PATCH] swap eval contexts for <(...) and >(...)

X-seq: zsh-workers 54324
From: Jun T <takimoto-j@xxxxxxxxxxxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: [PATCH] swap eval contexts for <(...) and >(...)
Date: Thu, 9 Apr 2026 17:22:26 +0900
Archived-at: <https://zsh.org/workers/54324>
In-reply-to: <35617ccc-13e9-472a-ad1f-ae9f3db73b8f@app.fastmail.com>
List-id: <zsh-workers.zsh.org>
References: <35617ccc-13e9-472a-ad1f-ae9f3db73b8f@app.fastmail.com>

> 2026/04/09 15:02, dana <dana@xxxxxxx> wrote:
> 
> the documentation for zsh_eval_context says:
> 
>  insubst
>    The <(...) form of process substitution.
>  outsubst
>    The >(...) form of process substitution.
> 
> but:
> 
>  % cat <( print -r - $zsh_eval_context )
>  toplevel outsubst
>  % : >( print -r - $zsh_eval_context )
>  toplevel insubst
> 
> swapped due to perspective confusion?

Isn't it better to "fix" the man page? I don't insist, but
in the case of<(...) what the sub-shell is doing now
(= current context) is "output".

# If we modify exec.c, it might break some existing scripts,
# although the possibility is _very_ low.

Follow-Ups:
- Re: [PATCH] swap eval contexts for <(...) and >(...)
  - From: dana

References:
- [PATCH] swap eval contexts for <(...) and >(...)
  - From: dana

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