Tammi 🥴🐈‍⬛

tamtararam@chaos.social

Tammi 🥴🐈‍⬛

tamtararam@chaos.social

You may find nsfw posts but with content warnings here. A filter with nsfw and lewd in it will be sufficient to hide these.

Hi I am ⚧️🏳️‍⚧️🐈‍⬛🤖
Computer witch that will curse your computer👩‍💻🧹 (patches your kernel)
Likes music 🎹 and audio things 🔊
Enjoys photography 📷 and video making 📹
Passively casts a calming spell on you when within range
Demi-Asexual Demigirl / Femby :nonbinary_flag:
Reader of appliance instruction manuals 📜

Vegetable Eater 🧄

2022-07-16 04:11:58 2022-07-16 04:11:57 2022-07-15 20:38:32 618401

mastodon - Link to source

Tammi 🥴🐈‍⬛

3 years ago • •

Tammi 🥴🐈‍⬛
3 years ago

Reminder for #bash and #shell script authors:
wizardzines.com/comics/bash-er…

errors:
by default, bash will continue after errors.
Bash: oh, was that an error? who care, let's keep running!
Programmer: Uh that is NOT what I wanted.
set -e stops the script on errors.
this makes your script WAY more predictable.
by default, unset variables don't error.
rm -rf "$HOME/$SOMEPTH".
bash: $SOMEPTH doesn't exist? no problem, i'll just use an empty string!
programmer: OH NOOO that means rm -rf $HOME.
set -u stops the script on unset variables.
bash: I've never heard of $SOMEPTH! STOP EVERYTHING!!!
by default, a command failing doesn't fail the whole pipeline.
curl yxqzq.ca | grep 'panda'
bash: curl failed but grep succeeded so it's fine! success!
set -o pipefail makes the pipe fail if any command fails.
you can combine set -e, set -u and set -o pipefail into one command I put at the top of all my scripts:
set -euo pipefail

bash errors

^{wizard zines}

#shell #bash

Languages
Search Text
Share via ...

⇧