zsh-users
 help / color / mirror / code / Atom feed
From: Shawn Halpenny <paxunix@gmail.com>
To: zsh-users@zsh.org
Subject: No pipefail option?
Date: Fri, 4 Oct 2013 08:59:49 -0700	[thread overview]
Message-ID: <CADv1Z=pM7H4Xg9+GyWd4zw0cv0mXfbJvqip6vc7e_yrXRN=1sg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 381 bytes --]

It seems like it would be a good bash-compatibility option to have
available.  I know we can check $pipestatus, but often I simply want to
abort the script if any command in the pipeline failed without having to do
an explicit check (similarly to how the errexit option works).  Explicit
checks too easily get forgotten or overlooked or even just implemented
incorrectly.

--Shawn

             reply	other threads:[~2013-10-04 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 15:59 Shawn Halpenny [this message]
2013-10-05 21:31 ` 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='CADv1Z=pM7H4Xg9+GyWd4zw0cv0mXfbJvqip6vc7e_yrXRN=1sg@mail.gmail.com' \
    --to=paxunix@gmail.com \
    --cc=zsh-users@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).