From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-17263-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 13023 invoked from network); 30 May 2002 15:48:58 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 30 May 2002 15:48:58 -0000
Received: (qmail 26537 invoked by alias); 30 May 2002 15:48:51 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 17263
Received: (qmail 26524 invoked from network); 30 May 2002 15:48:51 -0000
Date: Thu, 30 May 2002 08:48:47 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Sender: schaefer@ns1.sodaware.com
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: zsh: Strange feature with 'jobs' commmand
In-Reply-To: <Pine.LNX.4.44.0205300708110.3617-100000@ns1.sodaware.com>
Message-ID: <Pine.LNX.4.44.0205300848030.3617-100000@ns1.sodaware.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 30 May 2002, Bart Schaefer wrote:

> However, the code that does the traversing/printing of the job table is
> littered with tests to silence it when the process is not the foreground
> shell -- it'd be really tricky to make `jobs' do something useful while
> still preventing `bg' and `fg' from doing something broken.

Apparently I spoke too soon.