summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2022-07-20 09:42:22 -0700
committerSean Whitton <spwhitton@spwhitton.name>2022-07-20 10:10:42 -0700
commit183b3ec74a21416e06e6f9340cc39cfde5c85aa1 (patch)
treecc757388b7fa3d5043e29199995adac5d14c6ad1
parentb326984149d1537311d6b41441460d2ba5fee591 (diff)
downloaddotfiles-183b3ec74a21416e06e6f9340cc39cfde5c85aa1.tar.gz
have '!' and M-u advance to the next message
-rw-r--r--.emacs.d/init.el14
1 files changed, 13 insertions, 1 deletions
diff --git a/.emacs.d/init.el b/.emacs.d/init.el
index 990bd720..a7e1aebc 100644
--- a/.emacs.d/init.el
+++ b/.emacs.d/init.el
@@ -3088,9 +3088,21 @@ mutt's review view, after exiting EDITOR."
(gnus-summary-mark-forward n mark gnus-inhibit-user-auto-expire)
(save-excursion (gnus-summary-mark-forward n mark))
(gnus-summary-next-unread-article))))
+
+;; See (info "(gnus) Generic Marking Commands").
(with-eval-after-load 'gnus-sum
(define-key gnus-summary-mode-map [remap gnus-summary-mark-as-read-forward]
- #'spw/gnus-summary-mark-as-read-forward))
+ #'spw/gnus-summary-mark-as-read-forward)
+
+ ;; Given how we use flagging, described above, it makes sense to advance to
+ ;; the next message after flagging ...
+ (define-key gnus-summary-mode-map [remap gnus-summary-tick-article-forward]
+ #'gnus-summary-put-mark-as-ticked-next)
+
+ ;; ... and then for consistency we want M-u the same as '!' and 'd'.
+ ;; (We might otherwise just leave M-u with its default behaviour.)
+ (define-key gnus-summary-mode-map [remap gnus-summary-clear-mark-forward]
+ #'gnus-summary-put-mark-as-unread-next))
;; Unlike `notmuch-extract-thread-patches' and
;; `notmuch-extract-message-patches', it does not make sense to check out a