From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1884 invoked by alias); 7 Feb 2010 18:20:49 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 27680 Received: (qmail 24597 invoked from network); 7 Feb 2010 18:20:37 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received-SPF: pass (ns1.primenet.com.au: SPF record at ntlworld.com designates 81.103.221.48 as permitted sender) Date: Sun, 7 Feb 2010 18:20:28 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: have '&' automatically disown? Message-ID: <20100207182028.0f7c51ab@pws-pc> In-Reply-To: References: <19308.20198.797192.607014@gargle.gargle.HOWL> <201002051733.o15HXBZB025656@news01.csr.com> <201002051736.o15HaMlN025726@news01.csr.com> X-Mailer: Claws Mail 3.7.4 (GTK+ 2.18.6; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=W3tOLUehizD4qj6VhtReFuw5MKb8d+XqjIxlDsIazEA= c=1 sm=0 a=MwCwGuSUH9EA:10 a=0QhtZkFNAAAA:8 a=4UtWO5riAAAA:8 a=NLZqzBF-AAAA:8 a=xE9qsm9ZNsnh8Pz3cLQA:9 a=kLuuNKTAV-CAjW-H9RSV5pThEW8A:4 a=KLYB3oV4TgcA:10 a=Shd8Sdw-9eQA:10 a=_dQi-Dcv4p4A:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 On Fri, 05 Feb 2010 22:26:44 -0500 Greg Klanderman wrote: > Thanks for your response and clarification Peter, > > >>>>> On February 5, 2010 Peter Stephenson wrote: > > > When you "setopt monitor" again *then* jobs you didn't explicitly disown > > are reported. > > Really? That's not what I see, patchlevel 1.4847. I was probably too brief: when I said "reported", I meant "reported interactively when their state changes". I was assuming you were trying to ignore jobs to the extent that if you didn't look at them again, you wouldn't notice them, which is what turning off "monitor" should do for you, unless I've missed something. If you start going looking for them you'll still find them. I don't know if that's good enough for your needs or not. > It is the case that while monitor is off, 'jobs' does still list the > jobs, however 'fg' reports "fg: no job control in this shell.". I > turned monitor back on and 'fg'd a job, but now neither C-z nor C-c > will interrupt that job: I can well believe all of this, but it's not clear to me why its relevant. If it means you still need job control to work continuously, then certainly turning off "monitor" isn't an option. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/