From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
Date: Wed, 24 Mar 2004 08:54:40 +0100 [thread overview]
Message-ID: <9e8673aaefac7706fa9d27891bafeed9@plan9.escet.urjc.es> (raw)
In-Reply-To: <c9167f6cea8c715e0029b9f54cfe5a72@google.com>
> unwillingness to provide a 'grab'
> operation to lock out drawing access.
A grab that is timed out shouldn't be a problem.
At least if nobody but rio uses it.
Or is there something else?
next prev parent reply other threads:[~2004-03-24 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 18:53 andrey mirtchovski
2004-03-23 19:04 ` Russ Cox
2004-03-23 19:15 ` rog
2004-03-23 19:19 ` andrey mirtchovski
2004-03-23 19:30 ` rog
2004-03-23 19:45 ` rob pike, esq.
2004-03-23 23:49 ` Geoff Collyer
2004-03-24 4:35 ` rob pike, esq.
2004-03-24 7:54 ` Fco.J.Ballesteros [this message]
2004-03-23 19:50 ` rog
2004-03-23 19:51 ` rob pike, esq.
2004-03-23 19:47 ` rob pike, esq.
2004-03-23 20:09 ` boyd, rounin
2004-03-23 19:30 matt
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=9e8673aaefac7706fa9d27891bafeed9@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).