Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!purdue!decwrl!labrea!polya!weening@Gang-of-Four.Stanford.EDU
From: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Newsgroups: comp.windows.x
Subject: Re: Cursor droppings with X11R3 on the Sun 386i
Message-ID: <5058@polya.Stanford.EDU>
Date: 15 Nov 88 01:25:36 GMT
References: <3390@nicmad.UUCP> <8811141954.AA25317@EXPO.LCS.MIT.EDU>
Sender: news@polya.Stanford.EDU
Reply-To: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Organization: Stanford University
Lines: 14
In-reply-to: jim@EXPO.LCS.MIT.EDU (Jim Fulton)

In article <8811141954.AA25317@EXPO.LCS.MIT.EDU>, jim@EXPO (Jim Fulton) writes:
>
>Hmm, are you using R3 xterm, fonts, and server?  There was a bug in the R2
>xterm that caused it to display the "hollow" cursor in the wrong place (it
>was hidden by bugs in various R2 fonts).  If you are using all-R3 stuff and
>seeing the problem, do send a bug report with a full description of how to
>reproduce it (e.g. make sure you list which font).  

That explains it.  This was happening to me too, but now I see it
happens only when using an R2 xterm (typically on a host that hasn't
upgraded to R3 yet) with an R3 server.
-- 
Joe Weening                                Computer Science Dept.
weening@Gang-of-Four.Stanford.EDU          Stanford University