From a0344ffc3ad7844075f6b0bc53c5130545d5a1d5 Mon Sep 17 00:00:00 2001 From: StrawberryTea Date: Mon, 11 Mar 2024 03:01:48 -0500 Subject: [PATCH] fix(mu4e): advice for new mu4e release mu4e-quit now takes an optional argument, BURY, which is a boolean that determines whether to bury the buffer or kill it. This commit updates the advice to reflect this change. --- modules/email/mu4e/autoload/mu-lock.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/email/mu4e/autoload/mu-lock.el b/modules/email/mu4e/autoload/mu-lock.el index 14cf1b01d..6f1a111cd 100644 --- a/modules/email/mu4e/autoload/mu-lock.el +++ b/modules/email/mu4e/autoload/mu-lock.el @@ -35,9 +35,9 @@ If STRICT only accept an unset lock file." (when (or strict (/= (emacs-pid) pid)) t)))) ;;;###autoload -(defun +mu4e-lock-file-delete-maybe () +(defun +mu4e-lock-file-delete-maybe (&optional bury) "Check `+mu4e-lock-file', and delete it if this process is responsible for it." - (when (+mu4e-lock-available) + (when (and (+mu4e-lock-available) (not bury)) (delete-file +mu4e-lock-file) (file-notify-rm-watch +mu4e-lock--request-watcher)))