Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: bug in message.el, message-forward-make-body-plain
Date: Wed, 01 Dec 2004 17:19:56 +0900	[thread overview]
Message-ID: <b9ysm6qv39v.fsf@jpl.org> (raw)
In-Reply-To: <yccsm6r9k26.fsf@monkeypuzzle.wc.cray.com>

>>>>> In <yccsm6r9k26.fsf@monkeypuzzle.wc.cray.com> Ted Stern wrote:

> message-forward ignores message-forward-ignored-headers when the prefix
> argument is non-nil.

> To demonstrate:  Change the value of message-forward-ignored-headers globally,

[...]

> Now enter any gnus group, and attempt to forward a message using
>     C-u C-c C-f
> Instead of removing all but 4 or 5 relevant headers, nothing is changed.
> The same error occurs with
>     M-4 C-c C-f

I wrote the code for it, and then, I found a note when I was
going to write the ChangeLog file.

2002-07-27  Simon Josefsson  <jas@extundo.com>

	* message.el (message-forward-make-body): Don't use
	`message-forward-ignored-headers' when doing a "raw" followup (it
	is important to preserve e.g. CTE).

To forbid removing any headers will be overkill, however
message-forward-ignored-headers contains CTE, such an important
header, even now by default.  I think excluding CTE from m-f-i-h
may not solve the problem.  It is because m-f-i-h is a user
option and users can include any headers in it.  Any ideas?



  reply	other threads:[~2004-12-01  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 20:08 Ted Stern
2004-12-01  8:19 ` Katsumi Yamaoka [this message]
2004-12-01 19:15   ` Ted Stern
2004-12-01 19:48   ` Romain Francoise
2004-12-01 21:39     ` Ted Stern
2004-12-01 21:56       ` Romain Francoise
2004-12-02  8:25         ` Katsumi Yamaoka
2004-12-02  9:09           ` Romain Francoise
2004-12-19 22:26     ` Kai Grossjohann
2004-12-20 18:06       ` Ted Stern

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=b9ysm6qv39v.fsf@jpl.org \
    --to=yamaoka@jpl.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).