Date: Fri, 24 Sep 2004 16:59:46 +0200 From: Dimitry Andric <dimitry@andric.com> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: Putinas Piliponis <Putinas.Piliponis@hansa.lt> Subject: Re: Could ARG_MAX be increased? Message-ID: <359635024.20040924165946@andric.com> In-Reply-To: <200409242315.31325.doconnor@gsoft.com.au> References: <217202CB5FF8AE439E263CE3D48ECB50686C37@honda.int.hansa.lt> <p06110411bd78c249333c@[128.113.24.47]> <20040923184648.GB775@gothmog.gr> <200409242315.31325.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
------------9713415F16672A0F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On 2004-09-24 at 15:45:23 Daniel O'Connor wrote: >> This and xargs -0 for the cases where filenames can contain whitespace >> works like a charm anywhere, anytime... > It's only a pitty that you can have newlines in filenames :) That shouldn't matter, since the -0 argument to xargs tells it to expect NUL characters *instead* of spaces or newlines. As long as NUL characters aren't allowed in filenames, it should work. :) Note that there's still a chance that the program actually called by xargs doesn't handle newlines or other weird characters in filenames properly, though... ------------9713415F16672A0F Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFBVDZisF6jCi4glqMRAqFsAJ4nSMM2LPadPY1ZUeGcVMQ01b0uBACcDoeS 9bHGzP9hmrYSECuSfgabSgE= =Tudz -----END PGP MESSAGE----- ------------9713415F16672A0F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?359635024.20040924165946>