Date: Fri, 20 Apr 2001 11:29:15 +0100 From: Brian Somers <brian@Awfulhak.org> To: Dima Dorfman <dima@unixfreak.org> Cc: Garance A Drosihn <drosih@rpi.edu>, "John W. De Boskey" <jwd@bsdwins.com>, Current List <freebsd-current@FreeBSD.ORG>, brian@Awfulhak.org Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <200104201029.f3KATF533872@hak.lan.Awfulhak.org> In-Reply-To: Message from Dima Dorfman <dima@unixfreak.org> of "Thu, 19 Apr 2001 22:08:42 PDT." <20010420050842.E8EA93E2F@bazooka.unixfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Garance A Drosihn <drosih@rpi.edu> writes:
> > Or maybe something to indicate where the list of arguments
> > should go in a command. Hrm. Let's say '-Y replstr' or
> > '-y[replstr]' (no blank after -y). If no [replstr] is
> > given on -y, it defaults to the two characters '[]'.
> > Then one might do:
> > cat big_file_list | xargs -y cp [] target_directory
>
> This is a great idea! I'm willing to implement it if nobody else
> wants to.
If you add this (which I think is a good idea), please make it option
free with {} as the default arglist and -i to override that string in
line with sysv's xargs:
find something | xargs cp {} target_directory
or
find something | xargs -i '[]' cp '[]' target_directory
Although it's possible to break something that uses a literal {} as
an argument, I think this is better than introducing semantics
that'll confuse people.
> Dima Dorfman
> dima@unixfreak.org
Cheers.
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104201029.f3KATF533872>