summaryrefslogtreecommitdiff
path: root/test/lisp/emacs-lisp/rx-tests.el
diff options
context:
space:
mode:
authorStephen Gildea <stepheng+emacs@gildea.com>2018-09-02 17:06:29 -0700
committerStephen Gildea <stepheng+emacs@gildea.com>2018-09-05 06:49:36 -0700
commite932395656b80cc30ba3a53d83bddf57339aef7d (patch)
tree65f6c8b6b4242c64ed9579715e4342dc185cf05a /test/lisp/emacs-lisp/rx-tests.el
parentbaa6ae8724fd4cd7631164a89bf8eed4ff79cfc0 (diff)
downloademacs-e932395656b80cc30ba3a53d83bddf57339aef7d.tar.gz
emacs-e932395656b80cc30ba3a53d83bddf57339aef7d.tar.bz2
emacs-e932395656b80cc30ba3a53d83bddf57339aef7d.zip
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.
Diffstat (limited to 'test/lisp/emacs-lisp/rx-tests.el')
0 files changed, 0 insertions, 0 deletions