From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] refresh problems with drawterm on x (freebsd)?
Date: Wed, 5 Mar 2003 13:50:52 -0500 [thread overview]
Message-ID: <200303051850.h25IoqG12559@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 05 Mar 2003 11:46:49 MST." <Pine.LNX.4.44.0303051145150.9453-100000@fbsd.cpsc.ucalgary.ca>
Russ wrote:
> Has anyone else encountered refresh problems
> using drawterm on XFree86 / FreeBSD? A few people
> here have intermittent problems but we can't seem
> to characterize them.
>
To which Andrey replied:
> Text will just disappear from acme and terminal windows. I wouldn't even be
> able to see the text in the menu options (though the green rectangle still
> appears)
>
> Is there a newer version of drawterm for bsd I could try?
The problem Andrey reports is the problem I've had under MacOS X.
Well, that and the colormap thing. I've not seen it under FreeBSD,
though I've probably got a slightly older version of drawterm installed
here.
- Dan C.
next prev parent reply other threads:[~2003-03-05 18:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 17:59 Russ Cox
2003-03-05 12:36 ` Philippe Anel
2003-03-05 18:46 ` andrey mirtchovski
2003-03-05 18:50 ` Dan Cross [this message]
2003-03-07 1:55 ` Kenji Arisawa
2003-03-07 6:14 ` andrey mirtchovski
2003-03-07 23:12 ` Russ Cox
2003-03-08 0:06 ` Geoff Collyer
2003-03-08 6:45 ` Kenji Arisawa
2003-03-13 9:55 ` Jeff Sickel
2003-03-13 12:11 ` Kenji Arisawa
2003-03-13 13:58 ` [9fans] Drawterm on MacOS X; weird colormap? Kenji Arisawa
2003-03-05 21:36 ` [9fans] refresh problems with drawterm on x (freebsd)? anyrhine
2003-03-05 20:18 ` Russ Cox
2003-03-05 21:55 ` anyrhine
2003-03-06 15:38 ` Philippe Anel
2003-03-06 14:08 ` Russ Cox
2003-03-06 14:16 ` Russ Cox
2003-03-07 16:19 ` Ralph Corderoy
2003-03-07 14:15 ` Russ Cox
2003-03-10 10:18 ` 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=200303051850.h25IoqG12559@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).