From: Matt Pharr <mmp@graphics.stanford.edu>
Subject: [Patch] pay attention to prefix argument for forwarding messages again
Date: 11 Nov 1999 14:52:20 -0800 [thread overview]
Message-ID: <kh0k8nor68r.fsf@abuffer.stanford.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
In the olden days, C-u C-c C-f would forward a message with all of the
headers and C-c C-f would forward a cleaned up version of it. With this
patch, C-u C-c C-f will still forward all of the headers, regardless of the
value of message-forward-ignored-headers. This is useful for example for
spam reporting, where all the headers are useful.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: prefix argument for forwarding patch --]
[-- Type: text/x-patch, Size: 1097 bytes --]
*** lisp/message.el~ Mon Nov 8 14:28:52 1999
--- lisp/message.el Thu Nov 11 14:47:25 1999
***************
*** 3835,3841 ****
(setq e (point))
(and message-forward-as-mime
(insert "<#/part>\n"))
! (when message-forward-ignored-headers
(save-restriction
(narrow-to-region b e)
(goto-char b)
--- 3835,3842 ----
(setq e (point))
(and message-forward-as-mime
(insert "<#/part>\n"))
! (when (and (not current-prefix-arg)
! message-forward-ignored-headers)
(save-restriction
(narrow-to-region b e)
(goto-char b)
*** lisp/ChangeLog~ Mon Nov 8 17:30:33 1999
--- lisp/ChangeLog Thu Nov 11 14:48:00 1999
***************
*** 1,3 ****
--- 1,9 ----
+ 1999-11-11 Matt Pharr <mmp@graphics.stanford.edu>
+
+ * message.el (message-forward): Pay attention to prefix argument
+ again and forward all headers when it is set, regardless of the
+ value of message-forward-ignored-headers.
+
1999-11-09 00:13:25 Lars Magne Ingebrigtsen <larsi@gnus.org>
* nnslashdot.el (nnslashdot-retrieve-headers): Skip the article
[-- Attachment #3: Type: text/plain, Size: 122 bytes --]
-matt
--
Matt Pharr mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>
reply other threads:[~1999-11-11 22:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=kh0k8nor68r.fsf@abuffer.stanford.edu \
--to=mmp@graphics.stanford.edu \
/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).