Lady @Lady@cat.family

@coriander i understand what they are trying to say but it is bad

@aescling @wallhackio case statements use § 2.14 Pattern Matching Notation which is absurd and far inferior to grep for any but the most basic usecase

@wallhackio i am just making fun of the posix shell but i am also making fun of you for tolerating it (and not just doing an if…elif…fi chain which does not require you to type esac)

@wallhackio e‐sac

@aescling @wallhackio https://stackoverflow.com/questions/42679090/what-is-an-icon-file

@aescling @wallhackio (did you know that a file with the name `Icon´ followed by a carriage return is how macOS has stored folder icons since forever? 🌠)

@aescling @wallhackio you are the operator of your computer, not POSIX

@aescling @wallhackio files cannot have newlines in them that is absurd

they can have spaces in them however,,

@aescling @wallhackio *find. find is for that.

file is just for getting the type of the file

@aescling @wallhackio file is for a recursive directory search but there is no reason why you can¦t call file in a makefile

@wallhackio if you are doing `${file%flac}mp3"´ anyway can¦t you just switch on file extension rather than making a call to `file´?

if it were me i would parallelize this by using GNU Make which has a parallelization option

probably, to get all the functionality you want, creating some default rules to generate a %.mp3 from a %.flac and a fallback match-anything rule that treats its target as a directory (using FORCE) with secondary expansion to set the child files as dependencies from the target name dynamically (i think that works…)

but i¦m sure there is a more sane way

@wallhackio this motherfucker typed esac