From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3201 invoked from network); 30 Nov 1999 15:29:44 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 30 Nov 1999 15:29:44 -0000 Received: (qmail 21952 invoked by alias); 30 Nov 1999 15:29:28 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2755 Received: (qmail 21943 invoked from network); 30 Nov 1999 15:29:28 -0000 Date: Tue, 30 Nov 1999 10:29:27 -0500 From: Clint Adams To: zsh-users@sunsite.auc.dk Subject: Re: No `you have running jobs.' message Message-ID: <19991130102927.B28014@dman.com> References: <991128184113.ZM28661@candle.brasslantern.com> <19991130161438.A23971@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <19991130161438.A23971@caerdonn.eurocontrol.fr>; from roberto@eurocontrol.fr on Tue, Nov 30, 1999 at 04:14:38PM +0100 > I've always liked the [t]csh behaviour of detaching jobs automatically > (automatic nohup)... Having to use disown/nohup is a small annoyance. tcsh is more complex than that. It will nohup jobs run with &, but upon exit will kill without warning any jobs that you suspend and background. Your annoyance can be alleviated by putting "setopt nohup" in the appropriate startup file.