[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55620: [PATCH] 29.0.50; Eshell doesn't reset `eshell-in-pipeline-p'
From: |
Jim Porter |
Subject: |
bug#55620: [PATCH] 29.0.50; Eshell doesn't reset `eshell-in-pipeline-p' in subcommands |
Date: |
Tue, 24 May 2022 20:37:01 -0700 |
(Originally mis-sent with the wrong email address.)
Attached is a patch with tests to fix this. Note that I reset
`eshell-in-pipeline-p' in two places:
1. `eshell-subcommand-bindings': This handles any case where a
subcommand is invoked. This can happen with the following syntaxes:
{CMD}, ${CMD}, and $<CMD>.
2. `eshell-command-to-value': This handles cases where a command is run
synchronously. This can happen with some of the syntaxes mentioned
above: {CMD} and ${CMD}. However, it can also happen for Lisp forms like
(LISP) and $(LISP). (Most Lisp forms aren't likely to consult
`eshell-in-pipeline-p', but if you were calling an Eshell built-in
command using Lisp syntax, you might run into this issue.)
0001-Reset-eshell-in-pipeline-p-when-interpolating-comman.patch
Description: Text document