diff options
author | brian m. carlson <sandals@crustytoothpaste.net> | 2021-01-03 18:23:00 -0600 |
---|---|---|
committer | dana <dana@dana.is> | 2021-04-10 17:56:39 -0500 |
commit | f7a417388c73e7cfefb8e93fa8beba193fb1dd1f (patch) | |
tree | 9ddf4a641ed40e4efb685da05cf856e26ed449f1 /ChangeLog | |
parent | 408a83048366a22bf7645b71bee7428743793736 (diff) | |
download | zsh-f7a417388c73e7cfefb8e93fa8beba193fb1dd1f.tar.gz zsh-f7a417388c73e7cfefb8e93fa8beba193fb1dd1f.tar.xz zsh-f7a417388c73e7cfefb8e93fa8beba193fb1dd1f.zip |
47794: exec: run final pipeline command in a subshell in sh mode
zsh typically runs the final command in a pipeline in the main shell instead of a subshell. However, POSIX specifies that all commands in a pipeline run in a subshell, but permits zsh's behavior as an extension. The default /bin/sh implementations on various Linux distros and the BSDs always use a subshell for all components of a pipeline. Since zsh may be used as /bin/sh in some cases (such as macOS Catalina), it makes sense to have the common sh behavior when emulating sh, so do that by checking for being the final item of a multi-item pipeline and creating a subshell in that case. From the comment above execpline(), we know the following: last1 is a flag that this command is the last command in a shell that is about to exit, so we can exec instead of forking. It gets passed all the way down to execcmd() which actually makes the decision. A 0 is always passed if the command is not the last in the pipeline. […] If last1 is zero but the command is at the end of a pipeline, we pass 2 down to execcmd(). So there are three cases to consider in this code: • last1 is 0, which means we are not at the end of a pipeline, in which case we should not change behavior. • last1 is 1, which means we are effectively running in a subshell, because nothing that happens due to the exec is going to affect the actual shell, since it will have been replaced. So there is nothing to do here. • last1 is 2, which means our command is at the end of the pipeline, so in sh mode we should create a subshell by forking. input is nonzero if the input to this process is a pipe that we've opened. At the end of a multi-stage pipeline, it will necessarily be nonzero. Note that several of the tests may appear bizarre, since most developers do not place useless variable assignments directly at the end of a pipeline. However, as the function tests demonstrate, there are cases where assignments may occur when a shell function is used at the end of a command. The remaining assignment tests simply test additional cases, such as the use of local, that would otherwise be untested.
Diffstat (limited to 'ChangeLog')
-rw-r--r-- | ChangeLog | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog index 0e8a33f7c..c98923055 100644 --- a/ChangeLog +++ b/ChangeLog @@ -5,6 +5,10 @@ 2021-04-10 dana <dana@dana.is> + * brian m. carlson: 47794: README, Src/exec.c, + Test/B07emulate.ztst: exec: run final pipeline command in a + subshell in sh mode + * unposted (see 48415): README: Document incompatibility caused by workers/43928 |