Gnus development mailing list
 help / color / mirror / Atom feed
From: jidanni@jidanni.org
To: jdc@uwo.ca
Cc: ding@gnus.org
Subject: Re: nobreak-space totally gone
Date: Sun, 13 Sep 2009 23:26:38 +0800	[thread overview]
Message-ID: <878wgidfwx.fsf@jidanni.org> (raw)
In-Reply-To: <87skey2809.fsf@uwo.ca>

>>>>> "DC" == Dan Christensen <jdc@uwo.ca> writes:
DC> For several months I've also had a problem that when I reply to some
DC> messages, many of the space characters in the quoted text are replaced
DC> with underlines, although not the usual underline character.  For
DC> example, this is happening with the quoted text below.  I believe this
DC> often happens with nbsp characters in html messages.

DC> Can I get rid of this behaviour somehow?

Well, I wouldn't want an automated solution, lest I not know what is
going on. Imagine me, computer pro, sending bytes I was not aware of.

So I would run
shell-command-on-region  "uni2ascii -e" :
C-u M-| uni2ascii -e

Note as I don't have relatives constantly sending me nbsp's that I want
to quote, the above does not become a pain.

And me, computer pro, must not also read bytes I am not aware of, (at
least not in mail, HTML or not. Browsing actual web pages are a
different matter) hence I'll opt for the

(add-hook
 'gnus-article-mode-hook
 (lambda ()
   ;; Gnus sets it to nil in the article buffer locally.
   (setq nobreak-char-display t)))

solution mentioned, as I being a font dummy, better not mess more
intensely.



  reply	other threads:[~2009-09-13 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vdjw72i7.fsf@jidanni.org>
2009-09-06 11:17 ` jidanni
2009-09-07 13:34   ` Dan Christensen
2009-09-13 15:26     ` jidanni [this message]
2009-09-10  8:31   ` Katsumi Yamaoka
2009-09-10 11:43     ` Katsumi Yamaoka
2009-09-10 14:43       ` Ted Zlatanov

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=878wgidfwx.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=ding@gnus.org \
    --cc=jdc@uwo.ca \
    /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).