Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://cijber.social/users/gremlins/statuses/113032913672466277">Gremlins, Inc. (it/its) ♿ 🖕 (gremlins@cijber.social)'s status on Tuesday, 03-Sep-2024 08:24:30 JST</a><a href="https://cijber.social/@gremlins" title="gremlins@cijber.social"><img src="https://gnusocial.jp/avatar/226747-48-20250110142339.webp" width="48" height="48" alt="Gremlins, Inc. (it/its) ♿ 🖕" style="position: absolute; left: 0; top: 0;">Gremlins, Inc. (it/its) ♿ 🖕</a><div><a href="https://infosec.exchange/@darkuncle/113032028521655044" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/94607" title="darkuncle@infosec.exchange">Scott Francis</a></li></ul></div></section><article><p><a href="https://infosec.exchange/@darkuncle">@darkuncle</a> <a href="https://social.jvns.ca/@b0rk">@b0rk</a> <a href="https://cijber.social/tags/altText4u" rel="tag">#altText4u</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3576202#notice-7070265">In conversation</a><time datetime="2024-09-03T08:24:30+09:00" title="Tuesday, 03-Sep-2024 08:24:30 JST">about 9 months ago</time> <span>from <span><a href="https://cijber.social/@gremlins/113032913672466277" rel="external" title="Sent from cijber.social via ActivityPub">cijber.social</a></span></span><a href="https://cijber.social/@gremlins/113032913672466277">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3115381">"errors" comic strip by Julia Evans @b0rkpanel 1: 
"by default, bash will continue after errors" beneath is a bash-box saying "oh, was that an error? who cares, let's keep running!!!" and a programmer saying "uh that is NOT what I wanted""set -e stops the script on errors" with a programmer beneath saying "this makes your scripts WAY more predictable" next to words "set -e /n unzip fle zip" and a note pointing to the .zip line "typo! script stops here!"panel 2: "by default, unset variables don't error" followed by "rmb-r "$HOME/$SOMEPTH" and a bash box "$SOMEPTH doesn't exist? no problem, I'll just use an empty string!" and a programmer "OH NOOOO that means rm -rf $HOME"then "set -u stops the script on unset variables" followed by "set -u /n rm -r "$HOME/$SOMEPTH" and a bash box saying "I've never heard of $SOMEPTH! STOP EVERYTHING!!!"panel 3: "by default, a command failing doesn't fail the whole pipeline" followed by "curl yxqzq.ca | grep 'panda'" and a bash box saying "curl failed but grep succeeded so it's fine! success!" then "set -o pipefail makes the pipe fail if any command fails" followed by "you can combine set -e, set -u, and set -o pipefail into one command I put at the top 9f all my scripts: 'set -euo pipefail'"</a></label><br><a href="https://cijber.social/system/media_attachments/files/113/032/882/092/889/836/original/1d878ab74bfe3604.jpg" rel="external">https://cijber.social/system/media_attachments/files/113/032/882/092/889/836/original/1d878ab74bfe3604.jpg</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Gremlins, Inc. (it/its) ♿ 🖕 (gremlins@cijber.social)'s status on Tuesday, 03-Sep-2024 08:24:30 JSTGremlins, Inc. (it/its) ♿ 🖕
in reply to
- Julia Evans
- Scott Francis
@darkuncle @b0rk #altText4u
In conversationabout 9 months ago from cijber.socialpermalink
Attachments
1. "errors" comic strip by Julia Evans @b0rk panel 1: "by default, bash will continue after errors" beneath is a bash-box saying "oh, was that an error? who cares, let's keep running!!!" and a programmer saying "uh that is NOT what I wanted" "set -e stops the script on errors" with a programmer beneath saying "this makes your scripts WAY more predictable" next to words "set -e /n unzip fle zip" and a note pointing to the .zip line "typo! script stops here!" panel 2: "by default, unset variables don't error" followed by "rmb-r "$HOME/$SOMEPTH" and a bash box "$SOMEPTH doesn't exist? no problem, I'll just use an empty string!" and a programmer "OH NOOOO that means rm -rf $HOME" then "set -u stops the script on unset variables" followed by "set -u /n rm -r "$HOME/$SOMEPTH" and a bash box saying "I've never heard of $SOMEPTH! STOP EVERYTHING!!!" panel 3: "by default, a command failing doesn't fail the whole pipeline" followed by "curl yxqzq.ca | grep 'panda'" and a bash box saying "curl failed but grep succeeded so it's fine! success!" then "set -o pipefail makes the pipe fail if any command fails" followed by "you can combine set -e, set -u, and set -o pipefail into one command I put at the top 9f all my scripts: 'set -euo pipefail'"
  https://cijber.social/system/media_attachments/files/113/032/882/092/889/836/original/1d878ab74bfe3604.jpg

Public

Embed Notice

HTML Code

Corresponding Notice