9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rio on plan 9 from user space
Date: Sun, 29 May 2016 10:01:22 +0200	[thread overview]
Message-ID: <CAFSF3XMJcR_-=69WnX3fMvKJonT=WBOT+2iCGBfPTfTDJf6n2g@mail.gmail.com> (raw)
In-Reply-To: <2f8d64421a04911d6bc9f7815342dbfd@SDF.ORG>

Yes, rio needs whole display in Xorg. Xorg is a huge complex beast,
can't do the same things as on plan9 easily.

It makes no sense to me that you want to run *both* xfce and rio
anyway. Decide on the one that is more useful for you.

what's your latency to the cpu server? if you're limited by high
latency you might want to try 9front with 9front's drawterm, where
certain latency sensitive draw operations are optimized a lot more
than in plan9's version.


On 5/29/16, jfmxl <jfmxl@sdf.org> wrote:
> On another tack ... I have installed plan 9 from user space on my debian
> machine, and sam and acme seem to open and work ok. But when I type rio,
> I get ...
>
> $ rio
> rio: it looks like there's already a window manager running;  rio not
> started
>
> So, rio under plan 9 from user space (p9port?) wants the the whole
> display?
>
> I cannot run xfce and have rio in a window?
>
> I am trying to communicate with a plan 9 cpu, but drawterm seems slow
> and awkward.
>
> Are there any plan 9 installations open to people like myself to 'try
> out'?
>
>



  reply	other threads:[~2016-05-29  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29  6:32 jfmxl
2016-05-29  8:01 ` hiro [this message]
2016-05-29 14:48 ` Erik Quanstrom

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='CAFSF3XMJcR_-=69WnX3fMvKJonT=WBOT+2iCGBfPTfTDJf6n2g@mail.gmail.com' \
    --to=23hiro@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).