From owner-freebsd-current Thu Apr 19 22: 8:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 6B5B037B422 for ; Thu, 19 Apr 2001 22:08:43 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id E8EA93E2F; Thu, 19 Apr 2001 22:08:42 -0700 (PDT) To: Garance A Drosihn Cc: "John W. De Boskey" , Current List Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: ; from drosih@rpi.edu on "Fri, 20 Apr 2001 00:57:29 -0400" Date: Thu, 19 Apr 2001 22:08:42 -0700 From: Dima Dorfman Message-Id: <20010420050842.E8EA93E2F@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn 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. > you're trying to address. On the other hand, the man page > for 'xargs' on FreeBSD says: > > The xargs utility is expected to be IEEE Std 1003.2 > (``POSIX.2'') compliant. > > so I don't know how we go about adding options to it. On > the other hand, that same issue is faced by adding options > to 'cp', as there is a similar claim made in cp's man page. I don't think it's a problem. We're adding new options here, not changing--sometimes known as breaking--what already exists. I'm pretty sure that the standards don't say anything to the effect of, "You must support this and nothing else." That'd be rather silly. Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message