From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: _[9fans]_libdraw_α_differ ences_between_plan_9__and_p9p
Date: Fri, 31 Mar 2006 17:13:59 -0500 [thread overview]
Message-ID: <823aebaeb0cf7b8e0392dada3d55c5ca@swtch.com> (raw)
In-Reply-To: <14ec7b180603311403o517faed6qb0901d1ce46c2376@mail.gmail.com>
>> the answer is i didn't understand that there was a bug in the draw
>> library; i was not sure if there was a little hidden magic on plan9 that
>> made that work
if a function call behaves differently between plan 9 and p9p
for no obvious & documented reason, that's always a bug.
the new drawterm works around this by turning off most of
the X optimizations. i got tired of working around the early
OS X X server.
russ
next prev parent reply other threads:[~2006-03-31 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 18:52 erik quanstrom
2006-03-31 22:03 ` _[9fans]_libdraw_α_differences_between_plan_9__and_p9p andrey mirtchovski
2006-03-31 22:13 ` Russ Cox [this message]
2006-03-31 23:06 ` quanstro
2006-03-31 22:51 ` Re:__[9fans]_libdraw_α_differ_ences_between_plan_9__and_p9p Charles Forsyth
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=823aebaeb0cf7b8e0392dada3d55c5ca@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).