[Emacs-diffs] master e932395: Do not call mh-next-msg from mh-junk-process-* fns

[Stephen Gildea]

branch: master
commit e932395656b80cc30ba3a53d83bddf57339aef7d
Author: Stephen Gildea <address@hidden>
Commit: Stephen Gildea <address@hidden>

    Do not call mh-next-msg from mh-junk-process-* fns
    
    * mh-junk.el (mh-junk-process-blacklist, mh-junk-process-whitelist): Do
    not call mh-next-msg.  Now that these functions are called from
    mh-execute-commands, they should not change the current message pointer.
    The calls to mh-next-msg are probably left over from when blacklist and
    whitelist message processing was done immediately.
---
 lisp/mh-e/mh-junk.el | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/lisp/mh-e/mh-junk.el b/lisp/mh-e/mh-junk.el
index 6122606..0a50e02 100644
--- a/lisp/mh-e/mh-junk.el
+++ b/lisp/mh-e/mh-junk.el
@@ -108,8 +108,7 @@ message(s) as specified by the option 
`mh-junk-disposition'."
     (mh-iterate-on-range msg range
       (message "Blacklisting message %d..." msg)
       (funcall (symbol-function blacklist-func) msg)
-      (message "Blacklisting message %d...done" msg))
-    (mh-next-msg)))
+      (message "Blacklisting message %d...done" msg))))
 
 ;;;###mh-autoload
 (defun mh-junk-whitelist (range)
@@ -164,8 +163,7 @@ classified as spam (see the option `mh-junk-program')."
     (mh-iterate-on-range msg range
       (message "Whitelisting message %d..." msg)
       (funcall (symbol-function whitelist-func) msg)
-      (message "Whitelisting message %d...done" msg))
-    (mh-next-msg)))
+      (message "Whitelisting message %d...done" msg))))