Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Vladimir Marek <Vladimir.Marek@oracle.com>
Newsgroups: gnu.bash.bug
Subject: Re: [IDEA] more granular shell options to fix errexit
Date: Thu, 3 Jan 2019 17:46:31 +0100
Lines: 33
Approved: bug-bash@gnu.org
Message-ID: <mailman.6729.1546534006.1284.bug-bash@gnu.org>
References: <00c8e3c7-1dd2-1154-da89-a31e1a6fb515@mail.mipt.ru>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Cc: bug-bash <bug-bash@gnu.org>
To: Ivan Pozdeev <vano@mail.mipt.ru>
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <00c8e3c7-1dd2-1154-da89-a31e1a6fb515@mail.mipt.ru>
User-Agent: Mutt/1.5.22.1-rc1 (2013-10-16)
Precedence: list
Xref: csiph.com gnu.bash.bug:15038

Hi,

[...]

> The following suggested options aim to eliminate all cases that still exist,
> outlined on the above link, where an exit code of a command is
> swallowed/ignored.

[...]

My take on this, purely from user's point of view is to be able to
instruct bash to exit any time any command returns non-zero value unless
the situation is handled in the code. That means inside of

if command;  then ...
or
command || blah

So what you suggested is something I would like to use. If I would to
have command which does not terminate

command || :

If I want to catch the return value

command && RET=$? || RET=$?
OUT=$(command) && RET=$? || RET=$?


Cheers
-- 
	Vlad