From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] native limbo
Date: Tue, 1 May 2001 18:36:56 +0100 [thread overview]
Message-ID: <20010501172941.8EFE119A06@mail.cse.psu.edu> (raw)
the main reason, in my view, why limbo seems so distinct from plan 9 is
that it runs in its own little box in its own little console in its own
little portion of the namespace.
changing the inferno draw device so that it was the same as plan 9's
(and hence emu could just use the plan 9 draw device, same as it uses
plan 9's /net) would go a long way towards lowering the barriers.
there's no real reason why the console always has to be visible; and
apparently it shouldn't be too difficult to get the emu window to
resize.
those changes, along with a 9p->styx (and vice versa) bridge could make
inferno much more tightly integrated with plan 9, while preserving its
useful "ultra-portability" properties.
if it was up to me (it isn't), i'd feel reluctant to start divorcing
limbo from emu - much of the power of limbo comes from the environment
in which it lives, which is essentially the whole of inferno.
i've hacked up my version of emu and wm so that the snarf buffer is
held in common with plan 9. so i can copy out of a charon in one emu
window and paste into a terminal window in another, or into acme. i
find that this minor change has lessened to a great extent the amount
of frustration i experience due to the two separate environments.
bridging the two plumb spaces would help a lot too.
cheers,
rog.
next reply other threads:[~2001-05-01 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 17:36 rog [this message]
2001-05-01 18:25 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 13:02 rog
2001-05-01 16:04 kazumi iwane
2001-05-01 17:30 ` 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=20010501172941.8EFE119A06@mail.cse.psu.edu \
--to=rog@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).