Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: For loop bug
- X-seq: zsh-workers 17685
- From: Philippe Troin <phil@xxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: For loop bug
- Date: 16 Sep 2002 17:08:40 -0700
- In-reply-to: <20020916204657.GA29752@xxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020913233156.324A31C0E9@xxxxxxxxxxxxxxxxxxxxxxxx> <871y7xs7yd.fsf@xxxxxxxxxxxxxxxx> <1020914045657.ZM12939@xxxxxxxxxxxxxxxxxxxxxxx> <87elbufs3q.fsf@xxxxxxxxxxxxxxxx> <1020916062550.ZM29286@xxxxxxxxxxxxxxxxxxxxxxx> <873cs9pz8a.fsf@xxxxxxxxxxxxxxxx> <20020916204657.GA29752@xxxxxxxxxxxxxxxxxxxxx>
- Sender: Philippe Troin <phil@xxxxxxxx>
Hans Dieter Pearcey <hdp@xxxxxxxxx> writes:
> On Mon, Sep 16, 2002 at 11:26:45AM -0700, Philippe Troin wrote:
> > "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx> writes:
> > > $i never has a chance to get set to 2.
> >
> > Got that part. Thanks for the clarifications.
> >
> > > } > Further, { } is not a subshell, so { [[ 2 == 2 ]] && exit 1; } would most
> >
> > Indeed. However my version of zsh does not exit: it goes on happily as
> > if nothing happened.
>
> Because, as above, $i never gets to 2, and so the [[ 2 == 2 ]] && exit 1
> is not reached.
You're absolutely right. No bugs here :-)
Phil.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author