From: "Rene H. Larsen" <rhl@traceroute.dk>
Subject: Re: Strange display problem
Date: 13 Nov 1999 03:16:04 +0100 [thread overview]
Message-ID: <87yac3t9uj.fsf@worldonline.dk> (raw)
In-Reply-To: <byr9hv4siw.fsf@bolzano.math.ethz.ch>
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
next prev parent reply other threads:[~1999-11-13 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 14:25 Rene H. Larsen
1999-11-12 15:51 ` Jan Vroonhof
1999-11-13 2:16 ` Rene H. Larsen [this message]
1999-11-15 15:46 ` Toby Speight
1999-11-15 17:39 ` Jan Vroonhof
1999-11-15 18:31 ` Rene H. Larsen
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=87yac3t9uj.fsf@worldonline.dk \
--to=rhl@traceroute.dk \
/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).