æʃliŋ, ring racers purropawgandist @aescling@cat.family

@compufox oh shit

@wallhackio i am fairly certain they purrobably meant “the next” but the pedant in me can never ignore that going to Reading is a valid read

@noracodes in one of my classes in college we watched a short documentary on the various discoveries that eventually forced the conclusion of the meteor that killed the dinosaurs and i will never get over the fact that the idea was just from some physicist going “huh… but what if?”

STAY THE FUCK OUT

https://soundcloud.com/nxcnation/ntn8

mornyawn btw . also @clock, what time is it

@vaporeon_ @wallhackio kimty time, mrrew

@vaporeon_ @wallhackio purrameter

@vaporeon_ @wallhackio basic parameter expansion was in the original Bourne shell; i would have been shocked if some take on it hadn’t been standardized

@vaporeon_ @wallhackio (i have not yet read this myself, ftr, but i know it’s there)

@vaporeon_ @wallhackio https://pubs.opengroup.org/onlinepubs/9799919799/idx/shell.html

@vaporeon_ im gonna eat the delicious bomb 🍴💣

@vaporeon_ @wallhackio yes but not all of bash’s fancy expansions. you definitely do not have arrays lol

@wallhackio @vaporeon_ anyway

purr the Pure Bash Bible, the double parentheses are an alternate C-style syntax fur for loops with apparently similar semantics

@wallhackio @vaporeon_ this is bash-specific territory, where many features are added and language complexity explodes. there are nice conveniences but the funkiness of the language on top of the already funky nature of POSIX shell makes me want to avoid it where pawsible

@wallhackio @vaporeon_ [ is an alternative name of the command test(1); it needs to be recognized as its own token

@vaporeon_ @wallhackio i do think shell purrogramming syntax is ultimately quite simple, but that is after i learned about a lot of little hurdles that used to confuse me too