Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!its63b!simon
From: simon@its63b.ed.ac.uk (Simon Brown)
Newsgroups: comp.unix.wizards
Subject: Re:  jobs broken in csh
Message-ID: <507@its63b.ed.ac.uk>
Date: Sat, 27-Jun-87 12:01:36 EDT
Article-I.D.: its63b.507
Posted: Sat Jun 27 12:01:36 1987
Date-Received: Sat, 4-Jul-87 17:42:49 EDT
References: <8003@brl-adm.ARPA>
Reply-To: simon@its63b.ed.ac.uk (Simon Brown)
Organization: Computer Science Department, Edinburgh University
Lines: 25

In article <8003@brl-adm.ARPA> franco@MIKEY.BBN.COM (Frank A. Lonigro) writes:
>	I did the same test under Ultrix 1.2 and got the same results.  I
>can't imagine this being a feature but it seems to be everywhere.  I looked
>into the source code for the 'csh' and all builtin commands such as 'jobs'
>and 'dirs' print their output to 'stdout', yet the command 'jobs | cat'
>gives you nothing and 'dirs | cat' gives you the expected output.
>

The ``jobs'' command prints information about the jobs that the shell is
managing. Pipelines are executed in subshells, so ``jobs | cat'' will
print information about jobs being run by the *subshell*, not the main
shell -- and the subshell has no jobs in its table, hence no output.

	%{
	    Simon!
	%}


-- 
----------------------------------
| Simon Brown                    | UUCP:  seismo!mcvax!ukc!its63b!simon
| Department of Computer Science | JANET: simon@uk.ac.ed.its63b
| University of Edinburgh,       | ARPA:  simon%its63b.ed.ac.uk@cs.ucl.ac.uk
| Scotland, UK.                  |
----------------------------------     "Life's like that, you know"