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.
This commit is contained in:
Thierry Volpiatto 2020-11-16 07:48:33 +01:00
parent d33d48665f
commit 0fbe6edc4e
No known key found for this signature in database
GPG Key ID: 08FDB07A7433A7F2
1 changed files with 2 additions and 2 deletions

View File

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