From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9Ports libdraw open-in-same-window
Date: Thu, 9 Mar 2006 22:34:37 -0500 [thread overview]
Message-ID: <6ef91f1149bcb15fc3f307c5bec98c41@swtch.com> (raw)
In-Reply-To: <CCEE9E07-0B77-4D8C-9FD5-2C30E15365CB@telus.net>
> I've been recycling the drawable, but I need to keep a cross-process
> lock there; what's a good way to keep a lock in P9P?
I don't know how you keep a cross-process lock anywhere.
In Plan 9, rio provides the terminal windows - there is no 9term.
If an app opens /dev/mouse (which rio provides), then rio knows
an app is taking over the window and stops doing the terminal
things for that window. You can't run sam inside acme - only
one program can open /dev/mouse at a time.
I'm less worried about sam inside acme than I am about
programs fighting over windows because of lack of coordination.
It sounds like this requires significant coordination between
the programs.
Russ
next prev parent reply other threads:[~2006-03-10 3:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 21:36 Paul Lalonde
2006-03-09 21:40 ` Russ Cox
2006-03-09 22:21 ` Paul Lalonde
2006-03-10 0:38 ` Russ Cox
2006-03-10 1:00 ` Paul Lalonde
2006-03-10 1:14 ` Russ Cox
2006-03-10 3:15 ` Paul Lalonde
2006-03-10 3:34 ` Russ Cox [this message]
2006-03-10 4:26 ` Paul Lalonde
2006-03-10 3:35 ` Russ Cox
2006-03-10 6:50 ` Bruce Ellis
2006-03-10 14:25 ` Russ Cox
2006-03-10 13:55 ` erik quanstrom
2006-03-10 14:29 ` Russ Cox
2006-03-10 14:53 ` erik quanstrom
2006-03-10 15:03 ` Russ Cox
2006-03-10 15:21 ` erik quanstrom
2006-03-10 15:26 ` Russ Cox
2006-03-10 17:08 ` 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=6ef91f1149bcb15fc3f307c5bec98c41@swtch.com \
--to=rsc@swtch.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).