From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and FreeBSD
Date: Thu, 13 Mar 2003 18:20:09 -0500 [thread overview]
Message-ID: <47b29f3c11488b44c50b2bc7a7c358f5@plan9.bell-labs.com> (raw)
In-Reply-To: <5.2.0.9.0.20030312171850.030086d0@pop.noos.fr>
XInitThreads() does not fix the problem
on the Thinkpad X21 we've been using as
a test case. I changed the code to allocate
a new XDisplay for the cursor code, so now
each different process has its very own
XDisplay to use. Regardless of whether
XInitDisplay is there, the glyph problem
persists.
I changed stringbg to paint only half
the background for debugging, but got faked out
by the fact that libframe does its own background
painting. Tomorrow perhaps.
Russ
next prev parent reply other threads:[~2003-03-13 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 16:33 Philippe Anel
2003-03-13 22:19 ` Russ Cox
2003-03-13 23:20 ` Russ Cox [this message]
2003-03-17 11:43 ` Boyd Roberts
2003-03-19 10:03 ` Douglas A. Gwyn
2003-03-21 9:59 ` Ralph Corderoy
2003-03-21 11:24 ` Philippe Anel
2003-03-21 18:49 ` Russ Cox
2003-03-21 19:44 ` Russ Cox
2003-03-24 10:12 ` Ralph Corderoy
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=47b29f3c11488b44c50b2bc7a7c358f5@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).