From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] looking for shell account on plan9 for porting multitail
Date: Thu, 3 Jul 2003 07:16:44 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307030707340.17988-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <3efee8ae$0$49100$e4fe514c@news.xs4all.nl>
On Thu, 3 Jul 2003, Folkert van Heusden wrote:
> Ok, the deal is: I want to port it to plan9. So, for that I need
> shell-access to a plan-9 system. Anyone who can give this to me?
you can run plan9 in a vmware image...
>
> Some other things: MultiTail uses pseudo-tty's and (n)curses: are these
> available on Plan9?
no..
but here's how you can go about implementing multitail in plan9:
#!/bin/rc
while (! ~ $#* 0) {
window tail -f $1
shift
}
next prev parent reply other threads:[~2003-07-03 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 9:36 Folkert van Heusden
2003-07-03 13:02 ` matt
2003-07-03 13:16 ` andrey mirtchovski [this message]
2003-07-03 19:54 ` Andrew
2003-07-05 0:55 ` Dan Cross
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=Pine.LNX.4.44.0307030707340.17988-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).