Strange display problem

Strange display problem

[Rene H. Larsen]

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

The attached message has a strange display artifact on my system.
Near the bottom of the mail, you'll find a line saying:

Kundeservice xxxx/tolu

Where the four characters before the slash (the ones represented by an
x here) are not updated properly, i.e. if I scroll the window, these
four characters will be replaced with whatever was on that position of
the screen before it was scrolled.  Point disappears when placed over
one of these characters.

I'm using a Mule enabled XEmacs 21.1.8 and a CVS PGnus as of a few
days ago.  I had the same problem with PGnus 0.96.

I hope this makes any sense.


[-- Attachment #2: Type: message/rfc822, Size: 2563 bytes --]

Received: from localhost [127.0.0.1] (root)
	by izzlazz.ournet.dk with esmtp (Exim 3.03 #1 (Debian))
	id 11mGwm-0001iZ-00; Fri, 12 Nov 1999 14:41:00 +0100
Delivered-To: renehl@imada.sdu.dk
Received: from mailhost.imada.sdu.dk
	by localhost with IMAP (fetchmail-5.1.3)
	for renehl@localhost (single-drop); Fri, 12 Nov 1999 14:41:00 +0100 (CET)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by gade.imada.sdu.dk (Postfix) with ESMTP id B12C71F
	for <renehl@imada.sdu.dk>; Fri, 12 Nov 1999 14:38:54 +0100 (MET)
Received: from relay2.inet.tele.dk ([194.182.149.111]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <19991112133854.WFJQ375.fepC.post.tele.dk@relay2.inet.tele.dk>
          for <renehl@post1.tele.dk>; Fri, 12 Nov 1999 14:38:54 +0100
Received: (qmail 39494 invoked by alias); 12 Nov 1999 13:38:53 -0000
Delivered-To: alias-list-majordom-og-driftstatus@list.inet.tele.dk
Received: (qmail 39490 invoked by alias); 12 Nov 1999 13:38:52 -0000
Delivered-To: alias-list-driftstatus-outgoing@list.inet.tele.dk
Received: (qmail 55356 invoked by uid 40007); 12 Nov 1999 13:38:51 -0000
Received: (qmail 58784 invoked from network); 12 Nov 1999 13:38:49 -0000
Received: from fw1.inet.tele.dk (HELO idefix.int.tele.dk) (193.163.158.4)
  by relay2.inet.tele.dk with SMTP; 12 Nov 1999 13:38:49 -0000
Received: (from nobody@localhost)
	by idefix.int.tele.dk (8.9.3/8.9.3) id OAA26010;
	Fri, 12 Nov 1999 14:38:41 +0100
Date: Fri, 12 Nov 1999 14:38:41 +0100
Message-Id: <199911121338.OAA26010@idefix.int.tele.dk>
From: Tele Danmark Internet Kundeservice <listmail@post.tele.dk>
To: Flere modtagere paa listen DRIFTSTATUS <driftstatus@list.inet.tele.dk>
Subject: driftstatus: Løst: Flowforstyrrelser for kabelmodem kunder d. 10/11-1999
Sender: owner-driftstatus@list.inet.tele.dk
Precedence: bulk
Reply-To: dev-null@list.inet.tele.dk

Man  konstaterede onsdag d. 10/11-1999 kl. 10:54 at kunder
med kabelmodem kan opleve datastop i op til 5 min. ad gangen.

Problemet er nu blevet løst

Vi beklager de gener, dette har medført.

Venlig hilsen

Tele Danmark Internet
Kundeservice     /tolu
-------------------------------------------------------------------
Denne besked er sendt via:
Tele Danmark Internets driftsinformationssystem.
Ønsker du ikke at modtage disse informationer i fremtiden kan du
afmelde dig på: http://www.inet.tele.dk/kontakt/afmeld.htm
Husk at afmelde dig med samme navn og email adresse, som du
tilmeldte dig med.
-------------------------------------------------------------------

From: Tele Danmark Internet Kundeservice <listmail@post.tele.dk>
To: Flere modtagere paa listen DRIFTSTATUS <driftstatus@list.inet.tele.dk>
Subject: driftstatus: Løst: Flowforstyrrelser for kabelmodem kunder d. 10/11-1999
Date: Fri, 12 Nov 1999 14:38:41 +0100
Message-ID: <199911121338.OAA26010@idefix.int.tele.dk>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2.1: Type: text/plain, Size: 668 bytes --]

From: Tele Danmark Internet Kundeservice <listmail@post.tele.dk>
To: Flere modtagere paa listen DRIFTSTATUS <driftstatus@list.inet.tele.dk>
Subject: driftstatus: Løst: Flowforstyrrelser for kabelmodem kunder d. 10/11-1999
Date: Fri, 12 Nov 1999 14:38:41 +0100
Message-ID: <199911121338.OAA26010@idefix.int.tele.dk>

Man  konstaterede onsdag d. 10/11-1999 kl. 10:54 at kunder
med kabelmodem kan opleve datastop i op til 5 min. ad gangen.

Problemet er nu blevet løst

Vi beklager de gener, dette har medført.

Venlig hilsen

Tele Danmark Internet
Kundeservice     /tolu
-------------------------------------------------------------------
Denne besked er sendt via:
Tele Danmark Internets driftsinformationssystem.
Ønsker du ikke at modtage disse informationer i fremtiden kan du
afmelde dig på: http://www.inet.tele.dk/kontakt/afmeld.htm
Husk at afmelde dig med samme navn og email adresse, som du
tilmeldte dig med.
-------------------------------------------------------------------

[-- Attachment #3: Type: text/plain, Size: 165 bytes --]


-- 
Echelon bait:
genetic Ortega assassination ECHELON Waco, Texas CIA militia Serbian
domestic disruption Semtex Delta Force supercomputer Ft. Bragg colonel
AK-47

Re: Strange display problem

[Jan Vroonhof]

N.B. I don't think this really a Gnus problem. What platform are you using?

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

> Near the bottom of the mail, you'll find a line saying:
> 
> Kundeservice xxxx/tolu

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?

If so, does the problem go away if you do?

(aset (specifier-instance current-display-table) 160 "<NBSPC>")

If so what font do you use? Does changing the font help.

Jan

Re: Strange display problem

[Rene H. Larsen]

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> N.B. I don't think this really a Gnus problem. What platform are you
> using?

It turns out that it isn't.  It's just that I hadn't seen this problem
outside of Gnus before.  I'm on a Debian GNU/Linux potato system.

> 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.

> 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>".

> 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.

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?
-- 
Echelon bait:
David John Oates FBI Qaddafi Rule Psix class struggle SDI Waco, Texas
Kennedy Roswell [Hello to all my fans in domestic surveillance]
Ft. Bragg DES Khaddafi munitions counter-intelligence

Re: Strange display problem

[Toby Speight]

Rene> Rene H. Larsen <URL:mailto:rhl@traceroute.dk>

0> In article <87yac3t9uj.fsf@worldonline.dk>, Rene wrote:

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

Emacs does something similar to this by default, following a discussion
I had with RMS two or three years ago.  I've not heard of it causing
any problems.

Re: Strange display problem

[Jan Vroonhof]

"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

Re: Strange display problem

[Rene H. Larsen]

Jan Vroonhof <vroonhof@frege.math.ethz.ch> writes:

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

[...]

> > 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.

If it doesn't cause any problems, I think it should.  This problem may
not be limited to the lucidatypewriter font.

Thanks for the reply.
-- 
Echelon bait:
COSCO class struggle constitution Janet Reno plutonium FSF bomb clones
assassination colonel PLO CIA White Water genetic Croatian