From cfb4688eff722f2d8aebbc67f46b64e5b4c19236 Mon Sep 17 00:00:00 2001
From: Glenn Morris
Date: Sat, 7 Feb 2009 03:03:57 +0000
Subject: (metamail-interpret-body): Remove Rmail-specific hack that is no
 longer appropriate to mbox Rmail.

---
 lisp/mail/metamail.el | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

(limited to 'lisp/mail')

diff --git a/lisp/mail/metamail.el b/lisp/mail/metamail.el
index db2b5acf5f9..497fe73e3dc 100644
--- a/lisp/mail/metamail.el
+++ b/lisp/mail/metamail.el
@@ -121,11 +121,21 @@ Its header part is not interpreted at all."
 	     (append metamail-switches
 		     (list "-b" "-c" contype "-E" encoding))))
 	(metamail-region end (point-max) viewmode nil nodisplay))
-      ;; Mode specific hack.
-      (cond ((eq major-mode 'rmail-mode)
-	     ;; Adjust the marker of this message if in Rmail mode buffer.
-	     (set-marker (aref rmail-message-vector (1+ rmail-current-message))
-			 (point-max))))
+      ;; This mode specific hack is no longer appropriate in mbox Rmail.
+      ;; Pre-mbox, we have just modified the actual folder, so we
+      ;; update the message-vector with the new end position of the
+      ;; current message.  In mbox Rmail, all we have done is modify a
+      ;; display copy of the message.  Note also that point-max is a
+      ;; marker in the wrong buffer: the message-vector contains
+      ;; markers in rmail-view-buffer (which is not in rmail-mode).
+      ;; So this hack actually breaks the message-vector.
+      ;; If you're calling this on the actual rmail-view-buffer (or a
+      ;; non-swapped rmail-buffer), you would still need this hack.
+      ;; But you're not going to do that.
+;;;      (cond ((eq major-mode 'rmail-mode)
+;;;	     ;; Adjust the marker of this message if in Rmail mode buffer.
+;;;	     (set-marker (aref rmail-message-vector (1+ rmail-current-message))
+;;;			 (point-max))))
       )))
 
 ;;;###autoload
-- 
cgit v1.2.1