From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25953 invoked from network); 29 Jun 2001 00:09:30 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Jun 2001 00:09:30 -0000 Received: (qmail 12422 invoked by alias); 29 Jun 2001 00:08:17 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 3975 Received: (qmail 12408 invoked from network); 29 Jun 2001 00:08:16 -0000 From: "Bart Schaefer" Message-Id: <010628170738.ZM8419@candle.brasslantern.com> Date: Thu, 28 Jun 2001 17:07:38 -0700 In-Reply-To: <20010628153316.B20290@yahoo.com> Comments: In reply to Gregory Margo "Functions that start Jobs" (Jun 28, 3:33pm) References: <20010628153316.B20290@yahoo.com> X-Mailer: Z-Mail Lite (5.0.0 30July97) To: gmargo@yahoo.com, zsh-users@sunsite.dk Subject: Re: Functions that start Jobs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 28, 3:33pm, Gregory Margo wrote: > Subject: Functions that start Jobs > I have a Function that starts a process in the background. > The Job created is "%2" instead of "%1". > Why is this? Because the function itself is job %1. It doesn't show up in the output of "jobs" because it's being executed within the current shell process, but it still has a job table entry. > How can I make it be the first Job? You can't. Even if the function didn't use up one job slot, what if there were some other background job already running? Why is it important that it be the first job?