Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [SOLVED] Libtool/zsh quoting problem: a zsh... bug?
- X-seq: zsh-workers 22239
- From: Andrey Borzenkov <arvidjaar@xxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [SOLVED] Libtool/zsh quoting problem: a zsh... bug?
- Date: Sun, 12 Feb 2006 10:54:11 +0300
- In-reply-to: <200602121046.07861.arvidjaar@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20060209233201.GA5875@fargo> <20060211181440.GA30984@xxxxxxxxxxxxx> <200602121046.07861.arvidjaar@xxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 12 February 2006 10:46, Andrey Borzenkov wrote:
> > One question I have is what to do about ${=1:"$@"}? In the patch above,
> > I chose to let the double quotes override the '='. If that is not
> > desired, change the new "if" to only trigger disallow an spbreak of 2:
> >
> > + if (spbreak == 1 && (*s == Dnull || *s == Snull))
>
> As long as it is documented ...
>
And BTW this will be consistent with manual: "Perform word splitting using the
rules for SH_WORD_SPLIT during the evaluation of SPEC, but regardless of
whether the parameter appears in double quotes This forces parameter
expansions to be split into separate words before substitution, using IFS as
a delimiter." So it is already documented.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD7umjR6LMutpd94wRAhUnAJ4nPVOQ+SUsZEvbrpPm451F4O1nPwCfYrnM
pIRowIN/pGHEAHESHEQN9Lg=
=4EYQ
-----END PGP SIGNATURE-----
Messages sorted by:
Reverse Date,
Date,
Thread,
Author