Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: bug with for and |&
- X-seq: zsh-workers 13307
- From: "Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>
- To: <zsh-workers@xxxxxxxxxxxxxx>
- Subject: RE: bug with for and |&
- Date: Fri, 22 Dec 2000 10:01:24 +0300
- Importance: Normal
- In-reply-to: <200012191348.OAA00591@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
>
> Peter Stephenson wrote:
>
> > The problem is general to cases where a current-shell construct
> on the left
> > of the pipeline contains an external command. It doesn't matter what's on
> > the right of the pipeline. The code on the left seems to be executing all
> > right.
> >
> > % exec 3>&2
> > % { ls; print Finished >&3 } |& cat
> > Finished
> >
> > and it hangs in zwaitjobs, waiting for the job to finish, which it never
> > does. Change `ls' to `print foo' and the problem goes away.
>
> Rats. I still can't reproduce it, neither with (on Linux), nor without
> (on DU) the patch. So I guess there must be some kind of race
> condition somewhere...
>
Sorry for "me too", but neither do I. It works here all right. It may well be
some uninitialized variable.
-andrej
Messages sorted by:
Reverse Date,
Date,
Thread,
Author