From 0fbe6edc4ee3a41a584fd7a6fed5c34c15061c5f Mon Sep 17 00:00:00 2001 From: Thierry Volpiatto Date: Mon, 16 Nov 2020 07:48:33 +0100 Subject: [PATCH] No need to call `read-only-mode` when buffer is already read-only In mu4e~view-gnus, mu4e-view-mode derive from gnus-article-mode which derive from gnus-mode which derive from special-mode: (get 'mu4e-view-mode 'mode-class) => special. --- mu4e/mu4e-view.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mu4e/mu4e-view.el b/mu4e/mu4e-view.el index d3101aa4..0cda497a 100644 --- a/mu4e/mu4e-view.el +++ b/mu4e/mu4e-view.el @@ -402,11 +402,11 @@ article-mode." (gnus-article-prepare-display)) (setq mu4e~gnus-article-mime-handles gnus-article-mime-handles) (setq mu4e~view-message msg) + ;; `mu4e-view-mode' derive from `gnus-article-mode'. (mu4e-view-mode) (setq gnus-article-decoded-p gnus-article-decode-hook) (set-buffer-modified-p nil) - (add-hook 'kill-buffer-hook #'mu4e~view-kill-buffer-hook-fn) - (read-only-mode))) + (add-hook 'kill-buffer-hook #'mu4e~view-kill-buffer-hook-fn))) (defun mu4e~view-kill-buffer-hook-fn () ;; cleanup the mm-* buffers that the view spawns