zsh-workers
 help / color / mirror / code / Atom feed
From: Johan Grande <nahoj@crans.org>
To: zsh-workers@zsh.org
Subject: Failed pipeline doesn't err_exit/return if complex command last
Date: Thu, 6 Jul 2023 01:18:36 +0200	[thread overview]
Message-ID: <0c1f1b1e-7d2b-ec6b-3044-dc25b6d5a4d5@crans.org> (raw)

Hi all,

I noticed a strange behavior when using a complex command in a pipeline.

With `set -eo pipefail`, a failing pipeline that ends in a complex
command will have non-zero status but not exit the script (or a function
with err_return):

     false | if true; then true; fi
     echo $?

=> prints "1", exits with 0

However, this only occurs if the `if` command is last. If we add a `|
true` at the end:

     false | if true; then true; fi | true
     echo $?

=> no output, exits with 1

Same with a while loop (I only checked these 2 complex commands):

     false | while read line; do true; done
     echo $?

=> prints "1", exits with 0

     false | while read line; do true; done | true
     echo $?

=> no output, exits with 1

It seems inconsistent to me that a complex command be treated just like 
a simple command in the middle of a pipeline but not at the end, making 
a "list" that has non-zero status but doesn't return/exit despite the 
options.

As a sanity check, I ran the examples with bash and the result is what I 
would expect in all 4 cases: no output, exit with 1.

I'm using zsh 5.8.1 (x86_64-ubuntu-linux-gnu).

-- 
Johan Grande


             reply	other threads:[~2023-07-05 23:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 23:18 Johan Grande [this message]
2023-07-05 23:45 ` Johan Grande
2023-07-06  9:44 ` Peter Stephenson
2023-07-08  4:31   ` Bart Schaefer
     [not found]   ` <cf275400-d63a-d991-3aa5-1543d20a2f42@crans.org>
2023-07-16 14:36     ` Peter Stephenson
2023-07-17 19:25       ` Johan Grande
2023-07-17 23:34   ` Bart Schaefer
2023-07-18  1:51     ` Bart Schaefer
2023-07-18 13:57       ` Peter Stephenson
2023-07-20  8:47         ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0c1f1b1e-7d2b-ec6b-3044-dc25b6d5a4d5@crans.org \
    --to=nahoj@crans.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).