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 BAA02648 for <mason@werple.mira.net.au>; Sat, 4 Nov 1995 01:54:56 +1100 (EST)
Received: by math.gatech.edu (SMI-8.6/SMI-SVR4)
	id JAA02466; Fri, 3 Nov 1995 09:25:57 -0500
Resent-Date: Fri, 3 Nov 1995 09:25:57 -0500
Old-Return-Path: <chs@nando.net>
From: chs@nando.net (Chip Salzenberg)
Message-Id: <9511031432.AA01436@nando.net.nando.net>
Subject: Re: Background jobs with no job control / disown bug?
To: pws@ifh.de (Peter William Stephenson)
Date: Fri, 3 Nov 1995 09:32:31 -0500 (EST)
Cc: zsh-workers@math.gatech.edu
In-Reply-To: <9511031128.AA24164@sgi.ifh.de> from "Peter William Stephenson" at Nov 3, 95 12:28:31 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"Rqd8i3.0.Sc.qPYcm"@euclid>
Resent-From: zsh-workers@math.gatech.edu
X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/523
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

According to Peter William Stephenson:
> 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.

How about spawning it from a subshell?

    % (sleep 30&)
    % jobs
    %

-- 
               Chip Salzenberg, aka <chs@nando.net>
        "Hey, it's the Miss Alternate Universe Pageant!"
          -- Crow T. Robot, MST3K: "Stranded In Space"