From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: bug in message.el, message-forward-make-body-plain
Date: Thu, 02 Dec 2004 17:25:15 +0900 [thread overview]
Message-ID: <b9yzn0xm7is.fsf@jpl.org> (raw)
In-Reply-To: <87hdn5y970.fsf@orebokech.com>
>>>>> In <87hdn5y970.fsf@orebokech.com> Romain Francoise wrote:
> Katsumi, what do you think?
I think your patch is the best solution. I've installed it.
>>>>> In <87y8ghyf39.fsf@orebokech.com> Romain Francoise wrote:
> 2003-10-29 Simon Josefsson <jas@extundo.com>
> * message.el (message-forward-make-body-plain): Remove ignored
> headers. Tiny patch from Andre Srinivasan <andre@e2open.com>.
> (message-forward-make-body-plain): Fix ARG=1.
> The test is weird:
> (when (and (not current-prefix-arg)
> message-forward-ignored-headers)
> how can current-prefix-arg be nil since you call this function from C-u
> C-c C-f? Its value is '(4) here... unless I'm missing something.
It is likely if a user has set message-forward-as-mime as nil
and uses the `C-c C-f' command. I guess that was the mere copy
of an old code. In addition, I noticed there's also a problem
similar to this when the `3 C-c C-f' command is used, and fixed
it. Anyway, I'm thankful to Ted and Romain who gave me a good
understanding.
BTW, even for raw forwarding, isn't there a demand to remove
some headers? For instance, a lot of Received headers will
usually be unnecessary. Furthermore, if a header such as the
following
Xref: localhost trash:99999
is forwarded, the person who wrote the message may be offended.
Of course, we can remove them manually, though.
next prev parent reply other threads:[~2004-12-02 8:25 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
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 [this message]
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=b9yzn0xm7is.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).