From 47a046c662e54e086c23940f9a0eeada5f4f6def Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Arne=20K=C3=B6hn?= <arne@chark.eu>
Date: Tue, 25 Apr 2017 16:40:41 +0200
Subject: [PATCH] advance after mark can now be disabled

The variable mu4e-headers-advance-after-mark can be set to nil if you
want to disable moving to the next mail after marking.
---
 mu4e/mu4e-headers.el | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/mu4e/mu4e-headers.el b/mu4e/mu4e-headers.el
index e27ec97a..0d596d2c 100644
--- a/mu4e/mu4e-headers.el
+++ b/mu4e/mu4e-headers.el
@@ -127,6 +127,12 @@ and offlineimap."
   :type 'boolean
   :group 'mu4e-headers)
 
+(defcustom mu4e-headers-advance-after-mark t
+  "With this option set to non-nil, automatically advance to the
+next mail after marking a message in header view."
+  :type 'boolean
+  :group 'mu4e-headers)
+
 (defcustom mu4e-headers-include-related t
   "With this option set to non-nil, not just return the matches for
 a searches, but also messages that are related (through their
@@ -1700,7 +1706,7 @@ argument."
 region if there is a region, then move to the next message."
   (interactive)
   (mu4e-mark-set mark)
-  (mu4e-headers-next))
+  (when mu4e-headers-advance-after-mark (mu4e-headers-next)))
 
 (defun mu4e~headers-quit-buffer ()
   "Quit the mu4e-headers buffer.