From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27167 invoked by alias); 7 Feb 2010 21:59:14 -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: 27684 Received: (qmail 14382 invoked from network); 7 Feb 2010 21:59:13 -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,DKIM_SIGNED, DKIM_VERIFIED autolearn=ham version=3.2.5 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.219.227 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=QbQ03FG5hMO29dNILDhgpK2nVrilJkeT1/pbY9K0c7I=; b=YQ1lAe6Z40i24uXv7Lb00CBxlZ6Y+rS99gmzXQSQZXJjZe6zj/PwgQj091rgvnqx1N 6fywDYizVw36Sv8aiyBVo9r9iv9JqpV/9Bhw91qijhsW24PHWy4XSNOxOE6DAsY4vIsB E4hD1hNiBHyp1MUF5Nc2iIpOdSo8deBBe6694= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wkf27S6GlOqK8AuPmekODG/gAuImGWnsRnVG7OxGwGj9JYiyMrpc+GDK+627Fl8diu vZb/6NGS3yJW2Z4GpVZ3V0YiSpyyuaOD5xVhR6/YDiBgS/+X9981TxzvWfrcfWp08CzW K3GI0YAV+nmjXOxLc3m1aJZmxyj/yeD4uxMkk= MIME-Version: 1.0 In-Reply-To: References: <19308.20198.797192.607014@gargle.gargle.HOWL> <201002051733.o15HXBZB025656@news01.csr.com> <201002051736.o15HaMlN025726@news01.csr.com> <20100207182028.0f7c51ab@pws-pc> Date: Sun, 7 Feb 2010 22:59:09 +0100 Message-ID: <237967ef1002071359y2b2b8bb9jea5717539aebf436@mail.gmail.com> Subject: Re: have '&' automatically disown? From: Mikael Magnusson To: gak@klanderman.net Cc: zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 On 7 February 2010 22:06, Greg Klanderman wrote: >>>>>> On February 7, 2010 Peter Stephenson wrote: > >> If you start going looking for them you'll still find them. > > Certainly not the end of the world... > >> I don't know if that's good enough for your needs or not. > > nohup + nocheckjobs does most of what I care about I guess. > I just noticed the later before starting this thread. > >> I can well believe all of this, but it's not clear to me why its >> relevant. > > Because if I turn monitor back on I can completely wedge my shell. > >> If it means you still need job control to work continuously, then >> certainly turning off "monitor" isn't an option. > > I don't actually want to use job control on the jobs started while > monitor was off, but since they are still there, chances are I will at > some point shoot myself in the foot. > > Would it make sense to just auto-disown when monitor is off? This will probably get really annoying quickly... _self_insert() { [[ ! -o monitor && $KEYS = '&' ]] && RBUFFER=!$RBUFFER; zle .$WIDGET; ((CURSOR++)) } -- Mikael Magnusson