From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from math.gatech.edu (euclid.skiles.gatech.edu [130.207.146.50]) by werple.net.au (8.7/8.7.1) with SMTP id XAA25587 for ; Fri, 3 Nov 1995 23:02:22 +1100 (EST) Received: by math.gatech.edu (SMI-8.6/SMI-SVR4) id GAA00716; Fri, 3 Nov 1995 06:33:25 -0500 Resent-Date: Fri, 3 Nov 1995 06:33:25 -0500 Old-Return-Path: Message-Id: <199511031136.GAA02019@redwood.skiles.gatech.edu> X-Mailer: exmh version 1.6.4 10/10/95 To: zsh-workers@math.gatech.edu Subject: Re: Background jobs with no job control / disown bug? In-reply-to: Your message of "Fri, 03 Nov 1995 12:28:31 +0100." <9511031128.AA24164@sgi.ifh.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Nov 1995 06:36:01 -0500 From: Richard Coleman Resent-Message-ID: <"J38BX.0.2B.4uVcm"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/522 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > It occurred to me that one way of avoiding a background job getting > job control (disown is not a sufficient method in a function) is to > unsetopt MONITOR, spawn the job, then setopt MONITOR again. This > nearly works. Unfortunately, > > % unsetopt monitor > % sleep 30 & > % setopt monitor > % jobs > [1] + running I had thought that adding a new pre-command `nojob' would be a good idea. But to do this right would probably require some work. I was thinking that this and `noalias' would both be good ideas. I havn't looked at how to implement them yet. rc