Re: Strange display problem

[Jan Vroonhof <vroonhof@frege.math.ethz.ch>]

"Rene H. Larsen" <rhl@traceroute.dk> writes:

[Somehow I middes this message on the auc.dk newsserver. I swicthed to
quimby for this one]

> > Those x's are character nr 160 (nobreakspace in latin-1). Does your
> > XEmacs also have problem if you do
> > 
> > (loop repeat 4 do (insert (char-to-string 160)))
> > 
> > in a scratch buffer?
> 
> Yep, these characters show exactly the same display artifacts.

OK, it is a font painting problem then.


> > If so, does the problem go away if you do?
> > 
> > (aset (specifier-instance current-display-table) 160 "<NBSPC>")
> 
> Sort of.  Now the characters just show as "<NBSPC>".

That was just to make result more apparent.

> > If so what font do you use? Does changing the font help.
> 
> The lucidatypewriter font has this problem, but the default courier
> font doesn't.  I'd hate to have to switch back to courier.

So this is a bug in the lucidatypewriter font/the X drawing mechanism.

> Do you think
> 
> (aset (specifier-instance current-display-table) 160 " ")
> 
> is a suitable workaround for this problem, or are there any pitfalls I
> haven't thought of?

I cannot think of problems any at the moment.
The question is whether this should be included by default.

Jan