Message-Id: <199709082300.TAA01676@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: Tue, 9 Sep 1997 00:55:16 +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.970814113020.6734A-100000@is> from "Eli Zaretskii" at Aug 14, 97 11:31:11 am
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

> > !     /* quoting is only recognized at the beginning of an argument */
> > !     else if (ep == bp && !quote && (*ep == '\'' || *ep == '"'))
> >       {
> 
> I didn't actually test this change, but if it indeed only allows
> quotes at the beginning of an argument, I think this is bad idea: it
> breaks wildcard expansion on LFN platforms for pathnames with embedded
> spaces.  Consider this:
> 
> 		  ls /*/'Program Files'
> 
> If you only allow the quote at the beginning, you cannot say such
> things, because the wildcard will have to be quoted as well.  The fact
> that the current version allows this is a feature, not a bug.
> 
> Can you explain what's the bug with names like i'vebeen.org is?
> Doesn't i\'vebeen.org work?

I think that response files should be able to parse whatever find,
ls and dir say. And all three of them print it as i'vebeen.org

It's probably no good idea to make parsing of response files different
from other arguments.

Any suggestions ?