I see I've become a command line snob because I was expecting two bash commands separated by a pipe.
agree, I would use bash for this
, would you like to help me learn how to solve this with bash?
hey, I just saw your reply, and also see that @teroyks
beat me to it.
He did it well! :)
My bash skills are good to a limit but especially any time I need regex stuff or conditionals, I find myself grabbing Python because I'm more comfortable building things with it.
Would love to see and learn how this could be done in bash!
Perhaps not the most elegant way (and uses a few more than two commands), but this is how I would have done it:
find . -iname "*.pdf" | while read F; do FILE=$(basename "$F"); NR=$(printf "%02d" "$(echo "$F" | sed "s/.*(\(.*\)).*/\1/")"); cp -v "$F" "./Output/$NR - $FILE"; done
Could use internal bash functions instead of some of the external utilities, but internal shell logic is (at least for me) harder to remember than simple utility commands.
The biggest gotcha in handling file names is to remember to surround the values with quote marks when outputting them – otherwise, bash will split file names with spaces into several values, and everything will break.
This is so cool, thanks Tero for taking the time to educate!
Individually, all parts are familiar to me but I probably couldn't have constructed such a beautiful pipe.
I added this as an edit into the original post so people interested in bash scripting can also find it more easily.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.