@darius I mean it is an advanced topic.

@darius Can't hurt, but I've "learned" this at least 3 times and it's always easier to write a perl oneliner with `` than it is to figure out which xargs arguments count in the current situation.

a 2000 word `man` page, a lifetime to master

@darius i just pipe things into xargs and pass some random flags that seem nice hope for the best either it'll do exactly what i want or it'll delete everything — an exciting mystery!

@darius I’m at 40+ years of not using xargs. I think last month was only the second time where I decided it was worth figuring out (and then forgetting) the options. “find” and that weird “{} \;”, otoh, is embedded in my fingers.

@darius my tip is to use `xargs echo cmd` instead of `xargs cmd` so you can play around and see what would happen. less intimidating if you aren't worried about fucking up.

@darius xargs is the sound i make when i have to use xargs

@darius the -0 flag is a real lifesaver (combined with find -print0).

GNU parallel has been a useful tool for me in the past, too.

@darius I use GNU Parallel instead. It can run things in parallel but more fundamentally, it's xargs with a much better CLI.

@darius I cover it briefly in my article on unix tools, I mainly use it when I need to pass arguments around to multiple calls but am too lazy to write a full shell script for capturing output: https://billhunt.dev/blog/2015/05/10/unix-tools/

@darius It always takes me more time to figure out how to use it than it saves in processing time. But still worth it just for the joy of seeing parallel stuff happen, and the excitement of wondering if it will complete ok.

@darius regex before xargs

@darius I'm "scared to use spaces in filenames" old, so I recommend always "find -print0 | xargs -0" just in case there are any surprises

@darius I saw this on lobste.rs a while ago https://www.oilshell.org/blog/2021/08/xargs.html

@darius I hate it. Half of the common usage feels like compensating for shells with bad quoting rules or subprocess capabilities.

@darius I literally only finally learned last year, and I won't say it changed my life, and I still don't understand -0 but it's one of those niche things that is occasionally just a neat, elegant solution to a niggly cli problem

@darius xargs is simpler than it appears, and incredibly useful. i recommend also checking out gnu parallel

@darius I find I rarely need it. Between shell looping and non-dumb use of find, not much need.

find dir args -exec prog {} \; # dumb one at a time
find dir ars -print0 | xargs -0 prog {} # tedious so much typing
find dir args -exec prog {} + # nice, no xargs needed

for thing in $(find dir args) ; do
# handy loop, but $IFS sensitive
done

@darius if you need xargs you should *probably* be using a general purpose programming language

@darius Meanwhile, I will NOT learn how it works but I will pronounce it in a very silly way out loud while my puppy gives me a weird look

@darius first step is pronouncing it... which should be done with a heavy pirate accent

@darius If you figure it out, tell me, ok?