9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] command output on acme
Date: Fri,  8 May 2009 11:41:14 +0200	[thread overview]
Message-ID: <138575260905080241l370fa5d9re4a5011c49949ca3@mail.gmail.com> (raw)

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.
I think the way to go is to write something (probably an script) that
redirects the command's output to a single window by interacting with
the files in /mnt/acme/new and /mnt/acme/ID. Nevertheless I am not
quite sure on how to proceed with this, so any suggestions are
welcome.
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. Does acme
keep the pids of the external commands it runs somewhere so I can know
which ones I need to kill? in other words, say that I have 4 tail
commands running on some dir, with each of them showing their outputs
on its own window, how can I put the right argument to Kill on the
window tag so I can get rid of the command when I saw enough of the
file?
Saludos y gracias

--
Hugo



             reply	other threads:[~2009-05-08  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  9:41 hugo rivera [this message]
2009-05-08 14:34 ` Anthony Sorace
2009-05-08 14:50 ` erik quanstrom
2009-05-08 15:31 ` Russ Cox
2009-05-08 15:33 ` roger peppe
2009-05-08 18:59   ` Rob Pike
2009-05-11 14:03     ` hugo rivera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=138575260905080241l370fa5d9re4a5011c49949ca3@mail.gmail.com \
    --to=uair00@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).