Date: Wed, 25 Jun 2003 10:26:16 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: "Tim J. Robbins" <tjr@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: tcsh being dodgy, or pipe code ishoos? Message-ID: <20030625172616.GA57612@funkthat.com> In-Reply-To: <20030625192001.A10405@dilbert.robbins.dropbear.id.au> References: <20030624183515.A42570@FreeBSD.org> <1056499632.662.7.camel@timon.nist> <3EF922BE.4070803@acm.org> <20030624234707.A59666@FreeBSD.org> <20030625001525.A60867@FreeBSD.org> <20030625060450.GX57612@funkthat.com> <20030625074151.GY57612@funkthat.com> <20030625192001.A10405@dilbert.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim J. Robbins wrote this message on Wed, Jun 25, 2003 at 19:20 +1000:
> On Wed, Jun 25, 2003 at 12:41:51AM -0700, John-Mark Gurney wrote:
>
> [...]
> > So, now the question is, do we fix xargs to deal with unexpected
> > children? Or fix the shells in question? (tcsh and zsh seem to suffer
> > this problem)
> >
> > To me, fixing xargs is correct since it prevents another possible
> > future abusers of this "feature".
>
> Feel free to get rid of the -P option. What tcsh and zsh are doing is a fairly
> bad idea though, and it will break more than just xargs.
I think -P for xargs is a GOOD option. There are cases that this is
very useful. It is pretty trivial to fix too.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030625172616.GA57612>