From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9a3a1963917fe112e7978500e39cdc72@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  8 May 2009 10:50:50 -0400
To: 9fans@9fans.net
In-Reply-To: <138575260905080241l370fa5d9re4a5011c49949ca3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] command output on acme
Topicbox-Message-UUID: f6926016-ead4-11e9-9d60-3106f5b1d025

On Fri May  8 05:43:17 EDT 2009, uair00@gmail.com wrote:
> Hello,
> sometimes, when I execute a few times some external commands on a
> directory with multiple files on it (an external command like tail +0f
> on different files that are constantly appended), it is nice to have
> the output of each command on its own window, and not having all
> outputs mixed in /whatever/dir/+Errors.
[...]
> Also, when I have just one tail command running, acme's Kill command
> is fine when I no longer need it, but when you have >3 tail commands
> running at the same time, Kill doesn't work so good anymore.

perhaps this is why i'm such an inveterate user of win.  or maybe
it's the other way around.

either way, you can dodge both problems by doing tail -f in a win
window and using <del> to kill off your tail processes.

admittedly, this is an unsatisfying dodge.

- erik