uh oh bash scripts are fun
@wallhackio read the UNIX Programming Environment!!!
@wallhackio i developed a much better intuition fur how shell purrogramming works from reading its multiple chapters on the topic
@aescling the syntax is very confusing and i do not udnerstand what is happening half the time
☭
@wallhackio @aescling Reported 
(Which parts of the syntax are you confused by?)
@vaporeon_ @aescling for((i=0; i<${#files[@]}; i++)); do to loop over an array is not yet understood by me. the nested parenthesis, the # for some reason, what is @
@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
@vaporeon_ @wallhackio yes but not all of bash’s fancy expansions. you definitely do not have arrays lol
@aescling @wallhackio Where do I find documentation for POSIX shell?
@vaporeon_ @wallhackio (i have not yet read this myself, ftr, but i know it’s there)
@aescling @wallhackio Can confirm, parameter expansions are in there: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_06_02
@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
@aescling @wallhackio mrrrrrmrrrrrmrrrr 🐱
@vaporeon_ @wallhackio kimty time, mrrew
@wallhackio @vaporeon_ anyway
purr the Pure Bash Bible, the double parentheses are an alternate C-style syntax fur for loops with apparently similar semantics
@aescling @wallhackio Stupid question: Does POSIX shell have parameter expansions?