From 6bcf665c85e800421567b4735351e68b08c4de90 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Wed, 14 Dec 2022 22:37:56 +0200 Subject: [PATCH] mu4e-window: use mu4e-error Instead of the error. --- mu4e/mu4e-window.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mu4e/mu4e-window.el b/mu4e/mu4e-window.el index 6d8b3f9a..c8fc838b 100644 --- a/mu4e/mu4e-window.el +++ b/mu4e/mu4e-window.el @@ -151,7 +151,7 @@ tested." "Return non-nil if BUFFER is a detached view buffer." (with-current-buffer buffer (unless (mu4e-current-buffer-type-p 'view) - (error "Buffer `%s' is not a valid mu4e view buffer" buffer)) + (mu4e-error "Buffer `%s' is not a valid mu4e view buffer" buffer)) (null mu4e-linked-headers-buffer))) (defun mu4e--get-current-buffer-type () @@ -296,7 +296,7 @@ and `mu4e-headers-visible-lines' or This function is best called from the hook `mu4e-after-view-message-hook'." (unless (mu4e-current-buffer-type-p 'view) - (error "Cannot resize as this is not a valid view buffer.")) + (mu4e-error "Cannot resize as this is not a valid view buffer.")) (when-let (win (and mu4e-linked-headers-buffer (get-buffer-window mu4e-linked-headers-buffer))) ;; This can fail for any number of reasons. If it does, we do