From: Jim Davidson <jdavidso@nospam.com>
Subject: message forwarding and MIME
Date: Sat, 04 Dec 1999 00:59:41 GMT [thread overview]
Message-ID: <uwvqvmsde.fsf@liberate.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
I'm glad that the flag message-forward-as-mime made it into v .99.
It would be nice if the non-MIME behavior worked the same as for Gnus 5.7,
by inserting the start-separator and end-separator around the message.
The following patch (not in CVS) would do that.
--
Jim Davidson
jdavidso @ csi.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: insert separators around non-MIME forwarding --]
[-- Type: text/x-patch, Size: 1712 bytes --]
*** message.el.old Wed Dec 01 08:30:56 1999
--- message.el Fri Dec 03 16:24:02 1999
***************
*** 279,284 ****
--- 279,296 ----
:type 'file
:group 'message-headers)
+ (defcustom message-forward-start-separator
+ "------- Start of forwarded message -------\n"
+ "*Delimiter inserted before forwarded messages."
+ :group 'message-forwarding
+ :type 'string)
+
+ (defcustom message-forward-end-separator
+ "------- End of forwarded message -------\n"
+ "*Delimiter inserted after forwarded messages."
+ :group 'message-forwarding
+ :type 'string)
+
(defcustom message-make-forward-subject-function
'message-forward-subject-author-subject
"*A list of functions that are called to generate a subject header for forwarded messages.
***************
*** 3847,3859 ****
(message-goto-body)
(if message-forward-as-mime
(insert "\n\n<#part type=message/rfc822 disposition=inline>\n")
! (insert "\n\n"))
(let ((b (point))
e)
(mml-insert-buffer cur)
(setq e (point))
! (and message-forward-as-mime
! (insert "<#/part>\n"))
(when (and (not current-prefix-arg)
message-forward-ignored-headers)
(save-restriction
--- 3859,3872 ----
(message-goto-body)
(if message-forward-as-mime
(insert "\n\n<#part type=message/rfc822 disposition=inline>\n")
! (insert message-forward-start-separator))
(let ((b (point))
e)
(mml-insert-buffer cur)
(setq e (point))
! (if message-forward-as-mime
! (insert "<#/part>\n")
! (insert message-forward-end-separator))
(when (and (not current-prefix-arg)
message-forward-ignored-headers)
(save-restriction
next reply other threads:[~1999-12-04 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 0:59 Jim Davidson [this message]
1999-12-04 4:06 ` Emerick Rogul
1999-12-04 5:30 ` Kevin Falcone
1999-12-04 15:55 ` Emerick Rogul
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=uwvqvmsde.fsf@liberate.com \
--to=jdavidso@nospam.com \
/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).