Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: stopping "wait" in (sub)script ?
- X-seq: zsh-workers 3151
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Peter Stephenson <pws@xxxxxx>, zsh-workers@xxxxxxxxxxxxxxx (Zsh hackers list)
- Subject: Re: stopping "wait" in (sub)script ?
- Date: Thu, 15 May 1997 03:52:39 -0700
- In-reply-to: <199705150908.LAA28604@xxxxxxxxxxxx>
- References: <199705150908.LAA28604@xxxxxxxxxxxx>
On May 15, 11:07am, Peter Stephenson wrote:
} Subject: Re: stopping "wait" in (sub)script ?
}
} > > > $ for i in `cat ss`
} >
} > OK, now I got it. The fix looks really simple, and I do hope that this is
} > really al that's needed.
}
} This doesn't seem to fix this particular bug here, it's still
} uninterruptible. On the other hand, replacing `cat ss` with $(<ss)
} has always worked. That doesn't leave much code in getoutput() to
} make the difference.
I think the problem must be in signal_suspend(). The only difference
between the two cases in getoutput() is that $(<ss) does an explicit
child_unblock(), whereas `cat ss` does it implicitly via child_suspend(0).
If you go look at signal_suspend(), you'll find a lot of #ifdefs for the
assorted signal handling variations. I'll bet this problem is specific
to one or more of those variations.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
Messages sorted by:
Reverse Date,
Date,
Thread,
Author