Thanks to all for your advices. I am constantly amazed by acme's versatility.
Saludos
--
Hugo
A long time ago I wrote an rc program called 'new' that automated the
creation of a new window to hold a command's output.
It's installed in /acme/bin/new
-rob
2009/5/8 hugo rivera :
> 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
win takes a command to run as an argument.
win tail -f yourfile
would be almost exactly what you want.
You'd just delete the window when you're done watching.
The only problem is that on Plan 9, Del in the
new window doesn't send a "hangup" note to tail,
but it should.
% diff -c /n/sources/plan
On Fri May 8 05:43:17 EDT 2009, uai...@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
the solution for you depends, i guess, on how often you're doing this
and what the workflow really is, but if a bit of manual intervention
is okay, you have a ready-made solution: run command 1, change the tag
on the resulting window, run command 2. acme just looks for an
existing window with the e
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 /wha