From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9Ports libdraw open-in-same-window
Date: Thu, 9 Mar 2006 19:15:06 -0800 [thread overview]
Message-ID: <CCEE9E07-0B77-4D8C-9FD5-2C30E15365CB@telus.net> (raw)
In-Reply-To: <05a085ef4eedcefd3e4baa90523467fe@swtch.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ah, I see now. I'll go think on it some more, and write some more
code (can't have one without the other!)
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?
Paul
On 9-Mar-06, at 5:14 PM, Russ Cox wrote:
> If I run sam from inside acme, how does acme know
> not to draw over sam's screen? Does sam get a new
> X11 drawable that is above acme's?
>
> (For example, if I run sam inside acme and then in
> a separate window I run B /etc/passwd, presumably
> both sam and acme would try to display the file.)
>
> Russ
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEEO86pJeHo/Fbu1wRAoM7AJoDwF+eFWvlXtUnDph24K2VHaAyqACfRQN3
06Xq4/rXFNkP9qyBAQzfZQA=
=9m3V
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-10 3:15 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 [this message]
2006-03-10 3:34 ` Russ Cox
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=CCEE9E07-0B77-4D8C-9FD5-2C30E15365CB@telus.net \
--to=plalonde@telus.net \
--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).