Gnus development mailing list
 help / color / mirror / Atom feed
From: Emerick Rogul <emerick@cs.bu.edu>
Subject: [PATCH] Adds separators to non-MIME forwards (can someone apply?)
Date: 05 Apr 2000 19:50:27 -0400	[thread overview]
Message-ID: <vuovh1wjef0.fsf@csa.bu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

Can someone please apply this patch to the CVS gnus?

It adds the "------ Start of forwarded message -------" and "------
End of forwarded message ------" separators to non-MIME forwards.
This used to be standard in old versions of gnus, but has gone missing
as of late.

Thanks,

-Emerick

PS: This is my first time creating a patch, so I hope it works OK.  It
seemed to work fine for me.  :-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Adds start/end separators to non-MIME forwards --]
[-- Type: text/x-patch, Size: 762 bytes --]

--- message.old	Mon Mar 13 12:15:39 2000
+++ /home/alumni/emerick/message.el	Wed Apr  5 19:29:44 2000
@@ -3898,13 +3898,14 @@
     (message-goto-body)
     (if message-forward-as-mime
 	(insert "\n\n<#part type=message/rfc822 disposition=inline>\n")
-      (insert "\n\n"))
+      (insert "\n-------------------- Start of forwarded message --------------------\n"))
     (let ((b (point))
 	  e)
       (mml-insert-buffer cur)
       (setq e (point))
-      (and message-forward-as-mime
-	   (insert "<#/part>\n"))
+      (if message-forward-as-mime
+	   (insert "<#/part>\n")
+	(insert "\n-------------------- End of forwarded message --------------------\n"))
       (when (and (not current-prefix-arg)
 		 message-forward-ignored-headers)
 	(save-restriction

             reply	other threads:[~2000-04-05 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-05 23:50 Emerick Rogul [this message]
2000-04-20  0:37 ` Lars Magne Ingebrigtsen

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=vuovh1wjef0.fsf@csa.bu.edu \
    --to=emerick@cs.bu.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).