From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: non-break space
Date: Tue, 15 May 2007 18:00:55 +0200 [thread overview]
Message-ID: <v9lkfqhya0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mmz06z7gn.fsf_-_@jpl.org>
On Tue, May 15 2007, Katsumi Yamaoka wrote:
> Is it still necessary to prevent it from being displayed?
> Before it was introduced, the non-break space seems to have been
> displayed as `\ '.
Yes, that's why I've fixed the comment.
> But now it looks like `_' by default. I feel it looks better than a
> box.
If it's displayed as a box for you, there's something wrong. It
should be displayed exactly like an ordinary space character.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-05-15 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 1:47 Bug in copying Leo
2007-05-13 9:48 ` Reiner Steib
2007-05-15 10:50 ` non-break space (was Re: Bug in copying) Katsumi Yamaoka
2007-05-15 11:07 ` non-break space Michaël Cadilhac
2007-05-15 16:00 ` Reiner Steib [this message]
2007-05-15 23:31 ` Katsumi Yamaoka
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=v9lkfqhya0.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
/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).