From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20666 invoked from network); 14 Dec 1999 09:28:56 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Dec 1999 09:28:56 -0000 Received: (qmail 14198 invoked by alias); 14 Dec 1999 09:28:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9033 Received: (qmail 12342 invoked from network); 14 Dec 1999 09:13:50 -0000 Date: Tue, 14 Dec 1999 10:13:49 +0100 (MET) Message-Id: <199912140913.KAA28947@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Mon, 13 Dec 1999 17:42:21 +0000 Subject: Re: PATCH (and another bug report): Re: zsh script and SIGCONT 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. But still, somehow it feels wrong. Somehow I think it should either suspend the `.' or the loop (the top-level construct in the sourced file). The latter if we think of the sourced file as an equivalent of command line input. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de