oulx wrote:
Linda A. W. wrote:
I think this has been the case a few times. As for worrying about
quotes within my filenames, yes, it could be a concern, but quotes in file
names are less likely than spaces in my usage.
But that is just trading one problem for the same problem with a
different field
James Youngman wrote:
The program run by xargs is invoked directly with execvp(), and so the
arguments are not processed by the shell at all. This means that
spaces and other special characters in the file names (if they are
file names) are not treated specially at all. For this reason it
should
It would be nice if xargs had an option to enclose the arguments it reads
in in either double or single quotes before passing them to a program.
This would be especially useful for files with "spaces" in them.
:-)
Thanks,
Linda
___
Bug-findutils mailing
