From 285fdc5d5d1ca2acc6e0f307f7f710693f2fda3b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alex=20Benn=C3=A9e?= Date: Wed, 31 Mar 2021 10:04:03 +0100 Subject: [PATCH] mu4e/mu4e-headers: remove excess message output When marking threads as read things are slowed down by echoing the thread path to the mini-buffer. I assume this is left over debug but if needed for something else should probably be a log call. --- mu4e/mu4e-headers.el | 1 - 1 file changed, 1 deletion(-) diff --git a/mu4e/mu4e-headers.el b/mu4e/mu4e-headers.el index f43cb5cc..3b6c1018 100644 --- a/mu4e/mu4e-headers.el +++ b/mu4e/mu4e-headers.el @@ -1474,7 +1474,6 @@ descendants." (lambda (cur-msg) (let ((cur-thread-id (mu4e~headers-get-thread-info cur-msg 'thread-id)) (cur-thread-path (mu4e~headers-get-thread-info cur-msg 'path))) - (message "### %S %S %S" path match-path cur-thread-path) (if subthread ;; subthread matching; mymsg's thread path should have path as its ;; prefix