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 @
@vaporeon_ @aescling whitespace matters a lot which is surprising coming from c-style languages
like I tried to do if [! -d $dirname]; then and bash got mad at me for not putting a space between [ and !
Do not run this on your computer
@wallhackio @aescling Is Clodsire familiar with this invocation?
:(){ :|:& };:
re: Do not run this on your computer
@wallhackio @vaporeon_ @aescling who up forking they bomb
@vaporeon_ @wallhackio @aescling it looked to me like there was whitespace there so my dumb ass was staring at it trying to figure out why this would happen
@cam @wallhackio @aescling Sorry, I was specifically talking about [!, no whitespace in between, as opposed to [ !, yes whitespace in between...
@vaporeon_ @wallhackio @aescling it’s not your fault, I didn’t realize it was in monospace font so I was expecting it to look like [!
@wallhackio @vaporeon_ [ is an alternative name of the command test(1); it needs to be recognized as its own token
@wallhackio @aescling Yeah, that is confusing coming from C-style languages
If you type
[!, instead of invoking a command[with the arguments! -d $dirname], it tries to invoke a command[!, which does not exist...