Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: mail-header-separator starting with whitespace fails
Date: Tue, 13 May 2014 09:31:04 -0700	[thread overview]
Message-ID: <87r43xvdx3.fsf@windlord.stanford.edu> (raw)

Hello all,

I just upgraded to Emacs 24 from Emacs 23, with the corresponding change
in Gnus versions.  For the most part this went smoothly (thank you!).  But
there was one rather annoying hiccup that caused some problems, and I
thought I'd mention it somewhere so that people could consider whether
it's worth fixing.

I've never liked the default mail-header-separator in Emacs.  I think it
blends in with the header and the start of the body text.  So for years
I've used:

    (setq mail-header-separator (concat (make-string 39 ? ) "."))

to create a separator that's much less obtrusive.

Unfortunately, when upgrading from Emacs 23 to Emacs 24, something in Gnus
or in the underneath modes changed so that this mail-header-separator no
longer works.  It's appended to the Content-Type header (causing message
corruption if it has a charset setting), and then the first line of the
body is lifted into the headers and disappears.

Removing this setting fixes the problem, but brings back the default
message separator.

I did a little bit of poking around, and it looks like something inside
the Gnus message code isn't actually using mail-header-separator but
instead is looking for the first line in the buffer that doesn't look like
a header.  Since my message separator looked like a continuation line, it
skipped right past it and kept going.  This seems surprising to me.  I
think whatever is in mail-header-separator should always work, even if it
looks like a header.

-- 
Russ Allbery (eagle@eyrie.org)              <http://www.eyrie.org/~eagle/>



             reply	other threads:[~2014-05-13 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 16:31 Russ Allbery [this message]
2014-05-14  0:41 ` Katsumi Yamaoka
2014-05-16 23:35   ` Russ Allbery
2015-01-28  5:49   ` Lars Ingebrigtsen
2015-01-28  8:33     ` Katsumi Yamaoka
2015-01-29  1:47       ` Lars Ingebrigtsen
2015-01-29  2: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=87r43xvdx3.fsf@windlord.stanford.edu \
    --to=eagle@eyrie.org \
    --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).