Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Gnus picks up mail addresses in body when answering
Date: Thu, 24 May 2007 11:05:37 +0900	[thread overview]
Message-ID: <b4msl9nkmby.fsf@jpl.org> (raw)
In-Reply-To: <87r6p7vx8k.fsf@gate450.dyndns.org>

>>>>> In <87r6p7vx8k.fsf@gate450.dyndns.org>
>>>>>	Andreas Seltenreich wrote:

> Ack, ISTM message really wants to call message-narrow-to-head here
> instead of message-narrow-to-headers-or-head:

> --- message.el	9 Apr 2007 23:57:52 -0000	6.392.2.74
> +++ message.el	24 May 2007 01:10:08 -0000
> @@ -5867,7 +5867,7 @@
>    (let (follow-to mct never-mct to cc author mft recipients)
>      ;; Find all relevant headers we need.
>      (save-restriction
> -      (message-narrow-to-headers-or-head)
> +      (message-narrow-to-head)
>        ;; Gmane renames "To".  Look at "Original-To", too, if it is present in
>        ;; message-header-synonyms.
>        (setq to (or (message-fetch-field "to")

> Should we try to sneak this into Emacs 22?

`message-get-reply-headers' might be used by ones other than Gnus
and it might leave the header separator in the narrowed area but
is harmless since only `message-fetch-field' is performed there.
I can agree supposing no one binds `mail-header-separator' to
the one looking like a header. ;-)

Regards,



  reply	other threads:[~2007-05-24  2:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  6:00 Ralf Angeli
2007-05-24  1:00 ` Katsumi Yamaoka
2007-05-24  1:14   ` Andreas Seltenreich
2007-05-24  2:05     ` Katsumi Yamaoka [this message]
2007-05-24  1:48   ` Andreas Seltenreich
2007-05-24  5:57   ` Ralf Angeli
2007-05-24  8:07     ` Katsumi Yamaoka
2007-05-26  8:25   ` Reiner Steib
2007-05-28  2:14     ` 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=b4msl9nkmby.fsf@jpl.org \
    --to=yamaoka@jpl.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).