From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <19236d27e19c4ebbe4ba92e507e29149@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
From: rog@vitanuova.com
In-Reply-To: <c59798c7f2f4c588cd2cd337b831d30f@cwru.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 30 Mar 2004 17:25:46 +0100
Topicbox-Message-UUID: 47c679f2-eacd-11e9-9e20-41e7f4b1d025

> You need to put the brackets on the outside to make the combination of
> tail -f's act like a single 'tail -f'.  That was my real conceptual
> misunderstanding the first time around.

erm, i don't think so.

{a & b &}

should be exactly the same as

a & b &

you almost never need eval in rc, unless you genuinely want
to evaluate an rc expression that's unknown beforehand
(which isn't true in your case).

you could have got the behaviour i think you were after
with something like:

fn bt {
	x=$1
	shift
	for(i) {tail -f $i &}
	tail -f $x
}