Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15038 > unrolled thread

Re: [IDEA] more granular shell options to fix errexit

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [IDEA] more granular shell options to fix errexit Vladimir Marek <Vladimir.Marek@oracle.com> - 2019-01-03 17:46 +0100

#15038 — Re: [IDEA] more granular shell options to fix errexit

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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web