From: <markp@panix.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the "disappearing text problem" (experiment results)
Date: Mon, 6 May 2002 21:01:33 -0400 [thread overview]
Message-ID: <200205070101.g4711XA03820@panix1.panix.com> (raw)
| allocimage(display, Rect(0,0,1,1(, screen->chan, 1, 0x884488); /* some garish grapey thing */
that's a typo. I mean 0x884488ff, of course.
next reply other threads:[~2002-05-07 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:01 markp [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 0:25 markp
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=200205070101.g4711XA03820@panix1.panix.com \
--to=markp@panix.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).