nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3n409lc4d9w06xuqurrkkh4mtdzc2afc5m07tkkc26u7p2lcq04q2kq5wq (nprofile…q5wq)
More loatheworthy shell?
While one typically quotes things like in English with the opening quote at the beginning and the closing quote at the end, the shell is perfectly happy to accept things like
$ git commit -am Send\ the" output to "'"stdout"'
or even in the middle of words:
$ echo hell"o world"
⸻
Short-circuit boolean evaluation can be a blessing in short, clear contexts
$ some_prog && deploy || send_failure_notice
but can rapidly spiral into a world of subshells and implicit order-of-operations for the boolean-conjunction evaluations.
Also, various shells differ in how they handle wildcards on the right of "<" or ">"
$ cat < *
$ echo hello > *.txt
Does it behave like tee(1)? Or use the first one, expanding the rest as arguments to the program? Or is it an error? 🤷
I'm sure I could come up with a few more…
Emily! :Blobhaj_Witch_Broom: (nprofile…enrd) Piggo :verified_horse: (nprofile…q955)
Tim Chase /
npub1n5…ucr3d
2025-03-30 19:34:22
in reply to nevent1q…ufk4
Author Public Key
npub1n507nu5u0g0yy3jv8xzlwxzluyft9ps5p5etskrd6dxxlykkm8hqtucr3dPublished at
2025-03-30 19:34:22Event JSON
{
"id": "02c64a6bc2cbf2638e2b198b317edf1ddae694583316508267ba86c8bcacba39",
"pubkey": "9d1fe9f29c7a1e42464c3985f7185fe112b286140d32b8586dd34c6f92d6d9ee",
"created_at": 1743363262,
"kind": 1,
"tags": [
[
"p",
"8ceaf2ff15695cfd1b80e0c76b5ebb5b45857538a6dfe5dad856b9e0abf803ea",
"wss://relay.mostr.pub"
],
[
"p",
"9a21f9871d661e5c97f1ab72fd3cf71eb56584674938dc5984c4b8a8cf7f24f7",
"wss://relay.mostr.pub"
],
[
"p",
"aac4cd54dd3c8e2dc2d2472d27f255a9710188185f7a152f9626cd8c1d66c750",
"wss://relay.mostr.pub"
],
[
"p",
"967c6f3bb809d3ae791381503ec70d0da6a7ec7366f83b7c046e72d0a0748e98",
"wss://relay.mostr.pub"
],
[
"e",
"5de19b12ad8e74c7c3612ef028b4cd2f82d0d427d98c56975b891e8c6b739bdc",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.bsd.cafe/users/gumnos/statuses/114253054772854256",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3n409lc4d9w06xuqurrkkh4mtdzc2afc5m07tkkc26u7p2lcq04q2kq5wq \n\nMore loatheworthy shell?\n\nWhile one typically quotes things like in English with the opening quote at the beginning and the closing quote at the end, the shell is perfectly happy to accept things like\n\n$ git commit -am Send\\ the\" output to \"'\"stdout\"'\n\nor even in the middle of words:\n\n$ echo hell\"o world\"\n⸻\nShort-circuit boolean evaluation can be a blessing in short, clear contexts\n\n$ some_prog \u0026\u0026 deploy || send_failure_notice\n\nbut can rapidly spiral into a world of subshells and implicit order-of-operations for the boolean-conjunction evaluations.\n\nAlso, various shells differ in how they handle wildcards on the right of \"\u003c\" or \"\u003e\"\n\n$ cat \u003c *\n$ echo hello \u003e *.txt\n\nDoes it behave like tee(1)? Or use the first one, expanding the rest as arguments to the program? Or is it an error? 🤷 \n\nI'm sure I could come up with a few more…\n\nnostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqngslnpcavc09e9l34de0608hr66ktpr8fyudckvycju23nmlynmsl3enrd nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4tzv64xa8j8zmskjgukj0uj449csrzqctaap2tukymxcc8txcagqrjq955",
"sig": "315aa33201659c7bfa8b1bb41ecba16da97f1f9354a383d02a84b3b8e15bc364bcf4a13cc9776cccf4ea5eee73680e59d6608b83377881f64dcc8a89abace565"
}