Programming

17443 readers

239 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 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

POSIX.1-2024 has been published (ieeexplore.ieee.org)

submitted 5 months ago by mox@lemmy.sdf.org to c/programming@programming.dev

17 comments fedilink hide all child comments

A note from earlier today says the HTML edition will be available soon. I assume that means it will show up here: https://pubs.opengroup.org/onlinepubs/9699919799/

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

[–] flying_sheep@lemmy.ml -4 points 5 months ago* (last edited 5 months ago) (9 children)

Shell scripts were a mistake. The weirdness you have to remember to safely stop executing when something fails is mind-boggling.

I'm so glad nushell exists and doesn't need any configuring to just do the reasonable thing and stop executing when something fails.

[–] joyjoy@lemm.ee 1 points 5 months ago (4 children)

All you need to do is set -e at the start of the script to stop on a non-0 exit code. And quote variables to prevent globbing.

[–] flying_sheep@lemmy.ml 1 points 5 months ago (3 children)

Oh you sweet summer child.

If you don't use pipes or command substitutions, set -e gets you a fair part of the way there.

If you're interested, I can look up the rest of the arcane incantations necessary.

load more comments (2 replies)

load more comments (6 replies)