From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx os x
Date: Sun, 29 Jun 2008 12:09:58 -0700 [thread overview]
Message-ID: <20080629190959.2DE8E5B4B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 29 Jun 2008 14:16:10 EDT." <20080629181347.013C41E8C22@holo.morphisms.net>
On Sun, 29 Jun 2008 14:16:10 EDT "Russ Cox" <rsc@swtch.com> wrote:
> > Every time the option key is pressed, it generates 0xef8095
> > in addition to doing its button2 duty.
>
> Fixed.
Yup. Just tested it.
Another bug in both x11 and native mode 9vx: occasionally,
resizing the window can make it crash with a
9vx panic: sigsegv on cpu6
But of course when I try to cause it, it doesn't happen!
Also, quickly dragging the corner on the x11 version can
render the window completely black.
The native version is different from the x11 in the following ways:
- Top right acme `term' window doesn't open
- The top row in acme doesn't show win before newcol
- The window geometry is different.
- it has to be explicitly put in background.
A UI nit: the cursor shape doesn't change when moving it out
of the 9vx window.
When we do get to see a glenda icon for 9vx?:-)
A comment on networking: Since 9vx uses the host's IP stack,
two instances can't open the same port. But at least on
FreeBSD one can use jail(1) so that each 9vx instance has a
full complement of ports.
But this is good stuff! Thank you!
next prev parent reply other threads:[~2008-06-29 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 17:00 Russ Cox
2008-06-29 17:36 ` [9fans] " Francisco J Ballesteros
2008-06-29 17:55 ` Bakul Shah
2008-06-29 18:16 ` Russ Cox
2008-06-29 19:09 ` Bakul Shah [this message]
2008-06-30 1:56 ` Russ Cox
2008-06-30 5:42 ` underspecified
2008-06-30 8:46 ` jas
2008-06-30 17:37 ` Bakul Shah
2008-06-29 19:29 ` Pietro Gagliardi
2008-06-29 19:50 ` Axel Belinfante
2008-06-29 21:01 ` Francisco J Ballesteros
2008-06-29 21:27 ` Tom Lieber
2008-06-29 23:33 ` Fazlul Shahriar
2008-06-30 1:58 ` Russ Cox
2008-06-30 1:57 ` Russ Cox
2008-06-30 5:45 ` underspecified
2008-06-30 2:01 ` a
2008-06-30 15:38 ` David Leimbach
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=20080629190959.2DE8E5B4B@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).