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.
This commit is contained in:
StrawberryTea 2024-03-11 03:01:48 -05:00 committed by Yann Esposito (Yogsototh)
parent 22309ad240
commit 05dc179b96
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646

View file

@ -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)))