Hacker News Reader

I would expect xargs to stop processing arguments strictly after the first non-flag argument.

Arguments to xargs do appear to be parsed, example below:

http://explainshell.com/explain?cmd=find+%2F+-type+f+-print0...

Right, but in this example it's not telling me what the "grep" is doing. Admittedly xargs is a weird case where the arguments to the program are invoked as a program, but I'd say it shows pretty frequently in these type of "what does this long freaking command do?" situations. Maybe worth adding a special case for.

Reply on news.ycombinator.com