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

[dana <dana@xxxxxxx>]

On Thu 9 Apr 2026, at 03:22, Jun T wrote:
> 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.

i assumed the manual reflected the original intent because other pages
speak in those terms, but it does make sense both ways yeah

maybe pws can say definitively, it's been like that since he originally
added zsh_eval_context (27951)

i don't feel strongly myself, here's the opposite change if preferred

dana


diff --git a/Doc/Zsh/params.yo b/Doc/Zsh/params.yo
index ecedc3862..5904f74ad 100644
--- a/Doc/Zsh/params.yo
+++ b/Doc/Zsh/params.yo
@@ -1115,13 +1115,13 @@ item(tt(globsort))(
 Code executed to order files by the tt(o) glob qualifier.
 )
 item(tt(insubst))(
-The tt(<LPAR())var(...)tt(RPAR()) form of process substitution.
+The tt(>LPAR())var(...)tt(RPAR()) form of process substitution.
 )
 item(tt(loadautofunc))(
 Code read directly from a file to define an autoloaded function.
 )
 item(tt(outsubst))(
-The tt(>LPAR())var(...)tt(RPAR()) form of process substitution.
+The tt(<LPAR())var(...)tt(RPAR()) form of process substitution.
 )
 item(tt(sched))(
 Code executed by the tt(sched) builtin.