9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mayuresh Kathe <mayuresh@kathe.in>
To: 9fans@9fans.net
Subject: [9fans] rio : not completely rio-like : advice from packard!
Date: Wed,  3 Oct 2018 08:25:04 +0530	[thread overview]
Message-ID: <20181003025504.in6hj76aowwcrmaw@v520.kathe.in> (raw)

hi,

i just read that the rio in plan9port doesn't behave completely like the
rio in plan 9 because of problems inherent in x11/xorg.

could someone who understands x11/xorg well enough to have worked on
developing or enhancing rio under plan9ports please communicate with
keith packard? he's the god of x, and should be able to advise on a
solution either directly or as a work-around.

best,

~mayuresh




             reply	other threads:[~2018-10-03  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  2:55 Mayuresh Kathe [this message]
2018-10-03  5:07 ` Ori Bernstein
2018-10-03  8:01   ` hiro
2018-10-03 14:37     ` Sergey Zhilkin
2018-10-03 21:24       ` Aram Hăvărneanu

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=20181003025504.in6hj76aowwcrmaw@v520.kathe.in \
    --to=mayuresh@kathe.in \
    --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).