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 GitHub
parent b382255704
commit a0344ffc3a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -35,9 +35,9 @@ If STRICT only accept an unset lock file."
(when (or strict (/= (emacs-pid) pid)) t)))) (when (or strict (/= (emacs-pid) pid)) t))))
;;;###autoload ;;;###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." "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) (delete-file +mu4e-lock-file)
(file-notify-rm-watch +mu4e-lock--request-watcher))) (file-notify-rm-watch +mu4e-lock--request-watcher)))