From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-5524-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 29119 invoked from network); 26 Nov 2002 11:28:08 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 26 Nov 2002 11:28:08 -0000
Received: (qmail 26672 invoked by alias); 26 Nov 2002 11:27:49 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 5524
Received: (qmail 26657 invoked from network); 26 Nov 2002 11:27:46 -0000
To: zsh-users@sunsite.dk
Cc: Vincent Lefevre <vincent@vinc17.org>
Subject: Re: why does "jobs | wc" not work? 
In-reply-to: "Vincent Lefevre"'s message of "Tue, 26 Nov 2002 12:17:11 +0100."
             <20021126111711.GE27620@greux.loria.fr> 
Date: Tue, 26 Nov 2002 11:27:05 +0000
Message-ID: <14474.1038310025@csr.com>
From: Peter Stephenson <pws@csr.com>

Vincent Lefevre wrote:
> But with bash for instance, both
> 
>   jobs | cat
> 
> and
> 
>   true | jobs
> 
> work. So, it seems that jobs still works even in a child process.
> The same thing that 4.1 does?

It certainly looks like a similar hack of some sorts.  None of

   true | { jobs; }
   true | ( jobs; )
   function j { jobs; }; true | j

produce any output in the version of bash we have here (which probably isn't
up to date).  It so happens that with the hack we use, the special
case survives for the equivalent code on the left hand side of the pipe,
but a hack is a hack...

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************