Stephen Gildea e932395656 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.		2018-09-05 06:49:36 -07:00
..
ChangeLog.1
ChangeLog.2
mh-acros.el
mh-alias.el
mh-buffers.el
mh-comp.el	Fix mh-redistribute to work with nmh 1.5 and identities (SF#268)	2018-08-04 18:06:37 -07:00
mh-compat.el
mh-e.el
mh-folder.el
mh-funcs.el	Reset mh-blacklist and mh-whitelist on folder undo	2018-07-31 22:29:47 -07:00
mh-gnus.el
mh-identity.el	Fix mh-redistribute to work with nmh 1.5 and identities (SF#268)	2018-08-04 18:06:37 -07:00
mh-inc.el
mh-junk.el	Do not call mh-next-msg from mh-junk-process-* fns	2018-09-05 06:49:36 -07:00
mh-letter.el
mh-limit.el
mh-mime.el
mh-print.el
mh-scan.el
mh-search.el
mh-seq.el
mh-show.el
mh-speed.el
mh-thread.el
mh-tool-bar.el
mh-utils.el
mh-xface.el