After so many years of using bash I assumed that there is nothing special
to set -e that I wouldn't know so I didn't bother to look it up in the
docs, my bad. Thanks for the answers!
2018-06-11 16:09 GMT+01:00 Chet Ramey :
> On 6/11/18 6:12 AM, Bartłomiej Palmowski wrote:
>
> >
> > The issue is:
On 6/11/18 6:12 AM, Bartłomiej Palmowski wrote:
>
> The issue is:
> $ cat bad
> (
> set -e
> false
> echo "Shouldn't happen?"
> ) && :
> $ bash ./bad ; echo $?
> Shouldn't happen?
> 0
`set -e' is ignored for any command of an OR list except the last, whether
it is in effect before
On Mon, Jun 11, 2018 at 6:12 PM, Bartłomiej Palmowski
wrote:
>
> The issue is:
> $ cat bad
> (
> set -e
> false
> echo "Shouldn't happen?"
> ) && :
> $ bash ./bad ; echo $?
> Shouldn't happen?
> 0
> $ cat good
> (
> set -e
> false
> echo "Shouldn't happen?"
> )
> $ bash
$ lsb_release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:bionic
$ apt-cache show bash
Package: bash
Architecture: amd64
Version: 4.4.18-2ubuntu1
Multi-Arch: foreign
Priority: required
Essential: yes
Section: shells
