@darkuncle @b0rk #altText4u

(Medien: 1)

@darkuncle @b0rk habitually setting pipefail will drive you crazy next time you use grep -q.

@darkuncle @b0rk beware: `-o pipefail` is not defined in POSIX spec, so `/bin/sh` may not recognize it (`/bin/bash` would)

See ShellCheck Wiki for a POSIXly correct way of achieving a similar effect: https://www.shellcheck.net/wiki/SC3040

@darkuncle

One I find really helpful (but missing here) is 'set -x', that prints every line during execution.

@b0rk

@darkuncle @b0rk
except `set -e` has bizzare edge cases that can make you script behave in an unexpected way
http://mywiki.wooledge.org/BashFAQ/105

@darkuncle isn’t it great? I also enabled shellcheck/shfmt in my editor and it was transformative enough that I no longer think “this is a mistake” every time I start a non-trivial script (my bar for that is now non-scalar variables).

@darkuncle @b0rk and now you're doing it in the wrong shell, by making a single assumption.

@darkuncle Btw, there's perhaps an error, perhaps an oversimplification in the comic: the 'fail the whole pipeline' logic is, by default, the exit status of a pipeline command comes from the exit status of its final component. It's well documented and an old idea, although, in retrospect, perhaps not the best idea. Unix is full of such.

@b0rk

@darkuncle @b0rk I love this, but reading your replies reminded me why I am a computer science recluse. 😂