Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH (and another bug report): Re: zsh script and SIGCONT
- X-seq: zsh-workers 9042
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH (and another bug report): Re: zsh script and SIGCONT
- Date: Tue, 14 Dec 1999 14:21:06 +0100 (MET)
- In-reply-to: Sven Wischnowsky's message of Tue, 14 Dec 1999 10:13:49 +0100 (MET)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
I wrote:
> Bart Schaefer wrote:
>
> > ...
> >
> > So I was about to suggest that we should simply turn off MONITOR during
> > `.' and `source', since it's rather bizarre to have the loop keep going
> > leaving behind a trail of suspended jobs until the job table fills.
> > But then I tried in in bash -- where the lack of NOTIFY means that you
> > don't even find out about the string of suspended jobs until the loop
> > exits -- and now I'm not so sure.
>
> Interesting, hadn't thought about trying bash.
Just for the record: ksh makes the whole thing unsuspensible and tcsh
uses its usual cunning to suspend the sleep, exit loop and `source'
and leave you with only the suspended sleep as a job.
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author