Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: treatment of empty strings - why is this not a bug?
- X-seq: zsh-workers 26317
- From: Greg Klanderman <gak@xxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: treatment of empty strings - why is this not a bug?
- Date: Thu, 15 Jan 2009 15:28:11 -0500
- In-reply-to: <20090113220810.5ee564eb@pws-pc> (Peter Stephenson's message of "Tue, 13 Jan 2009 22:08:10 +0000")
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <18796.17298.94642.461735@xxxxxxxxxxxxxxxxxx> <20090113192409.0c21909a@pws-pc> <20090113220810.5ee564eb@pws-pc>
- Reply-to: gak@xxxxxxxxxxxxxx
>>>>> Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx> writes:
> For historical reasons, the usual behaviour that empty array elements
> are retained inside double quotes is disabled for arrays generated
> by splitting; hence the following:
Hi Peter, also could you please address my original question: when the
decision that unquoted parameter expansions in zsh should not undergo
field splitting was made, why was the behavior of dropping empty
strings retained?
thanks,
Greg
Messages sorted by:
Reverse Date,
Date,
Thread,
Author