On Fri, Oct 13, 2017 at 5:14 PM, Raul Miller <rauldmil...@gmail.com> wrote:
> On Fri, Oct 13, 2017 at 6:14 PM, Theo de Raadt <dera...@openbsd.org> > wrote: > > If you want to add things to standardized utilities you need to > > convince a large volume of people in the greater community > > > > Not me. > > Ok, > > Would you be open to a re-implementation of the gnu xargs -d option? > You want a version of xargs that, instead of requiring special handling for 5 characters legal in filenames (quote, double-quote, backslash, space, tab, newline), will be completely unable to handle exactly one of those characters (newline)? Easy: create this two line shell script under some convenient name and use it instead: #!/bin/sh sed 's!\(.\)!\\\1!g' | xargs "$@" My personal preference is to pick either of the following options: a) don't use any of those characters in filenames and just use xargs bare b) go directly into perl or C once I reach the limit of -0 option handling IMO, (a) makes sense for stuff you control the name of, (b) for stuff where you don't. The set of people I trust to create filenames containing space, tabs, or quotes, but not newlines is *empty*. Philip Guenther
