On 12/12/2012 12:54 PM, Pádraig Brady wrote:
On 12/12/2012 07:05 PM, Aaron Davies wrote:
Is there a reason the interface for readlink(1) is “FILE” instead of
“FILE...”? I’ve often wanted to do e.g. “find -type l|xargs readlink”
or (in zsh) “readlink **/*(@)”, and having to do a shell loop or use
“xargs -n1” seems inelegant.
Note the newer more general realpath(1)
supports multiple files.
Though there is no reason I see that readlink(1)
can't do so too. I also see the BSD version
can accept multiple args, so I'll probably add
something along the lines of the following
unless there are objections.
If you add support for handling more than one file at a time, then you
also should add support for separating the output with NUL instead of
newline to make the output unambiguous.