Commit e9323956 authored by Stephen Gildea's avatar Stephen Gildea

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.
parent baa6ae87
......@@ -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))))
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment