Notices by Tosti ? (tost@mk.toast.cafe), page 22

@aliss@outerheaven.club absolutely
if you go for strict POSIX compatibility, \e will NOT work, for instance
octals still should though
see https://www.mankier.com/1p/printf

@helene@p.helene.moe @aliss@outerheaven.club remind me to tell you about the pleroma deathrattle sometime
use that exact word, I'll know what it's about :totodile_laugh:

@aliss@outerheaven.club @helene@p.helene.moe nope !
you just go build and voila

@aliss@outerheaven.club @helene@p.helene.moe IME is "In My Experience"

@aliss@outerheaven.club @helene@p.helene.moe go isn't as painful to write in IME and the module system is nice and the lack of a build system is good

@aliss@outerheaven.club @helene@p.helene.moe it's "been" coming on and off for 3 years or so :totodile_laugh:
the short version is
"if I get off my ass, it is"

@aliss@outerheaven.club @helene@p.helene.moe I should be working on it right now tbh :apensive:

@aliss@outerheaven.club @helene@p.helene.moe the elixir/erlang vm

@aliss@outerheaven.club @helene@p.helene.moe (or better yet lua and co

@aliss@outerheaven.club @helene@p.helene.moe try go :nko_3c:

@aliss@outerheaven.club @helene@p.helene.moe tosti shell book :apensive:

@helene@p.helene.moe @aliss@outerheaven.club yes (though I'd rather BEAM let the system handle restarting stuff, rather than enter a death loop :nko_3c:

@aliss@outerheaven.club @helene@p.helene.moe also yes shellcheck is really bad and I hate it and cannot recommend anyone use it ever

@helene@p.helene.moe @aliss@outerheaven.club ;jnergwnegr;woengowg

@aliss@outerheaven.club @helene@p.helene.moe im not sure what POSIX says on case’s patterns behaviorokay, so

https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_04_05see Pattern Matching Notation
that is matched by the string resulting from the tilde expansion, parameter expansion, command substitution, arithmetic expansion, and quote removal of the given wordLet's go to Pattern Matching Notation: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13If any character (ordinary, shell special, or pattern special) is quoted, that pattern shall match the character itself. The shell special characters always require quoting.
When unquoted and outside a bracket expression, the following three characters shall have special meaning in the specification of patternsthis raises the question of what happens when you have a quoted variable expansion - is the expanded output considered quoted or not?
let's look at https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_02
which sends us to https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
. . . which has nothing to say on the matter

POSIX is ultimately an "unfinished" (or rather, incomplete - open to interpretation) specification, especially when it comes to shell
and this is where the potential differnence lies
welcome to hell

@aliss@outerheaven.club @helene@p.helene.moe it depends on how case(1b) functions
some shells have unqualified entries work as wildcards or terminators and it's wild
you should generally presume them to be "flat" strings

@aliss@outerheaven.club @helene@p.helene.moe shell dependent :^)

@helene@p.helene.moe @aliss@outerheaven.club the output is the pattern you put in, which means the pattern is what needs to go into the case-pattern (or something that'll match against it)

@helene@p.helene.moe @aliss@outerheaven.club let me make this a bit simpler to demonstrate the mechanismfor i in fake news fedora-logo-icon tm; do grep -qe "$i" /etc/os-release && break done echo "$i" # fedora-logo-icon on my machine

@helene@p.helene.moe @aliss@outerheaven.club you have to for this to ork