Message-Id: <199709101444.KAA20690@delorie.com>
From: Oberhumer Markus <k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at>
Subject: Re: c1args.c patches
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 10 Sep 1997 16:38:06 +0200 (METDST)
Cc: k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at, djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.970909143152.7143K-100000@is> from "Eli Zaretskii" at Sep 9, 97 02:32:44 pm
Return-Read-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

> For `find', this is a known problem, not specific to DJGPP (see the
> docs of Findutils for details).  If you use the list of file names
> with `xargs', try the -print0 switch to `find' and then use -0 option
> of `xargs'.  If you need to create a response file, pass the list of
> names through a Sed script that quotes them.  For example:

xargs has the annoying limitation of the size of the transfer buffer
which makes it useless in many cases - this was the idea behind
my '@-' extension to read a response file from stdin.

Would it make sense to extend parsing of response files so that
it can handle 'find -print0' by default - this shouln't be much work ?