Programming

25480 readers

566 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Error handling in bash (notifox.com)

submitted 1 day ago by BlackEco@lemmy.blackeco.com to c/programming@programming.dev

23 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] IanTwenty@piefed.social 5 points 18 hours ago (1 children)

Errors in command substitution e.g. $(cat file) are ignored by 'set -e', one example of its confusing nature. It does not force you to all handle errors, just some errors and which ones depends on the code you write.

https://mywiki.wooledge.org/BashPitfalls#set_-euo_pipefail

[–] Oinks@lemmy.blahaj.zone 3 points 8 hours ago* (last edited 8 hours ago)

This is a great article. I just want to highlight this insane behavior in particular (slightly dramatized):

set -e

safeDelete() {
  false

  # Surely we don't reach this, right?
  echo "rm $@ goes brr..."
}

if safeDelete all of my files; then
    : # do more stuff
fi

Frankly if you actually need robustness (which is not always), you should be using a real programming language with exceptions or result types or both (i.e. not C). UNIX processes are just not really up to the task.