From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] new memdraw troubles
Date: Wed, 8 Apr 2009 09:49:25 -0400 [thread overview]
Message-ID: <83aa7e55c6f7814e9b2bdce5b32201b2@quanstro.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
the attached image does lots of funny things.
mug (which probablly can't handle the image)
displays an image striped in the bottom half.
it's all black with a varying α, but displays all
black in faces with the new draw code, but
blue with the old (drawterm) code. togif
makes it blue again on plan 9 and under xv.
i haven't yet made much progress with this one.
- erik
[-- Attachment #2.1: Type: text/plain, Size: 326 bytes --]
from postmaster@brasstown:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: plan 9 image
Content-Disposition: attachment; filename=quanstro.net.1
Content-Transfer-Encoding: base64
[-- Attachment #2.2: quanstro.net.1.suspect --]
[-- Type: application/octet-stream, Size: 9276 bytes --]
reply other threads:[~2009-04-08 13:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=83aa7e55c6f7814e9b2bdce5b32201b2@quanstro.net \
--to=quanstro@quanstro.net \
--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).