From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16685 invoked from network); 24 Jun 1999 09:29:41 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 24 Jun 1999 09:29:41 -0000 Received: (qmail 24438 invoked by alias); 24 Jun 1999 09:29:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6821 Received: (qmail 24429 invoked from network); 24 Jun 1999 09:29:31 -0000 Message-Id: <9906240900.AA39221@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: loop killing In-Reply-To: "Sven Wischnowsky"'s message of "Thu, 24 Jun 1999 11:08:02 DFT." <199906240908.LAA27110@beta.informatik.hu-berlin.de> Date: Thu, 24 Jun 1999 11:00:53 +0200 From: Peter Stephenson Sven Wischnowsky wrote: > This is the solution which executes commands in a loop in the same > process group as the parent shell. This seems to be the neatest solution, covering most of the common things you want to do without any fuss. But at the moment something nasty is happening with shell functions. % fn() { less $*; } % fn glob.c ^Z If I type a few characters before hitting ^Z, then I get the `suspended' message, and the `continued' message when I type fg, but then the job immediately disappears again. Hmmm, that didn't seem to be working properly even before, except the problem then was that when I tried to continue it I got the message zsh: 39221 suspended (tty output) l glob.c so it looks like the process groups were already getting messed up. So maybe the new problem is just the old one appearing in a different place. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy