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 26331
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: treatment of empty strings - why is this not a bug?
- Date: Fri, 16 Jan 2009 19:45:29 -0800
- In-reply-to: <m363kfvy3u.fsf@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <18796.17298.94642.461735@xxxxxxxxxxxxxxxxxx> <090115201912.ZM20275@xxxxxxxxxxxxxxxxxxxxxx> <m38wpbw3v2.fsf@xxxxxxxxxxxxxx> <200901161755.n0GHt4aT025943@xxxxxxxxxxxxxx> <m363kfvy3u.fsf@xxxxxxxxxxxxxx>
On Jan 16, 2:40pm, Greg Klanderman wrote:
}
} If the NO_SH_WORD_SPLIT default is only to be the source of subtle
} bugs and not actually useful, then it should be removed.
I'd suggest that if the shell has been behaving this way for more than
15 years now, and a majority of its users consider the behavior to be
useful, that perhaps asserting that it is "only" a source of subtle
bugs is a tad presumptive.
} I don't see any reason you'd
} ever want the current behavior in a new script, and any existing
} script should just emulate to the broken behavior.
That's exactly backwards from the philosophy that zsh development has
always followed.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author