From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15795 invoked from network); 27 Mar 2001 06:54:17 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Mar 2001 06:54:17 -0000 Received: (qmail 11831 invoked by alias); 27 Mar 2001 06:54:05 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13784 Received: (qmail 11816 invoked from network); 27 Mar 2001 06:54:04 -0000 Date: Tue, 27 Mar 2001 08:54:02 +0200 (MET DST) Message-Id: <200103270654.IAA14212@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.dk In-reply-to: Peter Stephenson's message of Mon, 26 Mar 2001 15:29:03 +0000 Subject: Re: `jobs | wc -l' => 0 ... bug? Peter Stephenson wrote: > > From: neonatus@neonatus.net (Bostjan Muller) > > jobs | wc -l | tr -d " " > > but in zsh wc does not seem to get any input: > > $ jobs > > [1] - suspended mc > > [3] + suspended mc > > > > $ jobs | wc -l > > 0 > > jobs here runs in a subshell, where there is no job control, so no > information on jobs. It has always been this way. It's not particularly > convenient, however. Maybe it's time someone thought about changing it. > > The only workaround is to use a temporary file for output. But in zsh one can do that faster with ${#jobdirs} (or jobstates or jobtexts) anyway. After the parameter module is loaded. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de