9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] run rio in inferno?
Date: Wed, 24 Jan 2001 16:30:29 +0000	[thread overview]
Message-ID: <20010124162453.4850F199E8@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 232 bytes --]

some of us might like that or perhaps go even further.
some of the foundations were surveyed and even laid last year, but
there wasn't time to make the changes (and live with
them long enough to test) before the last release.


[-- Attachment #2: Type: message/rfc822, Size: 1479 bytes --]

To: cse.psu.edu!9fans
Subject: [9fans] run rio in inferno?
Date: Wed, 24 Jan 2001 13:56:19 +0000
Message-ID: <20010124135619.A24992@student.cs.ucc.ie>

is it possible to use rio instead of wm in inferno?

failing that, anybody working on a limbo port of rio?

             reply	other threads:[~2001-01-24 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 16:30 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-24 13:56 Vincent D Murphy

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=20010124162453.4850F199E8@mail.cse.psu.edu \
    --to=forsyth@vitanuova.com \
    --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).