From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22219 invoked from network); 14 Dec 1999 13:21:13 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Dec 1999 13:21:13 -0000 Received: (qmail 16448 invoked by alias); 14 Dec 1999 13:21:08 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9042 Received: (qmail 16441 invoked from network); 14 Dec 1999 13:21:08 -0000 Date: Tue, 14 Dec 1999 14:21:06 +0100 (MET) Message-Id: <199912141321.OAA03642@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Sven Wischnowsky's message of Tue, 14 Dec 1999 10:13:49 +0100 (MET) Subject: Re: PATCH (and another bug report): Re: zsh script and SIGCONT 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@informatik.hu-berlin.de