From 2b0d75b2953623c63c6afa3adb32ee48dee5851b Mon Sep 17 00:00:00 2001 From: djcb Date: Sun, 21 Feb 2016 16:33:55 +0200 Subject: [PATCH] mu4e: don't use message-kill-actions for closing frames Seems it is handled by the other actions already, and kills one-too-many frames. --- mu4e/mu4e-compose.el | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/mu4e/mu4e-compose.el b/mu4e/mu4e-compose.el index 41fa8416..a171e899 100644 --- a/mu4e/mu4e-compose.el +++ b/mu4e/mu4e-compose.el @@ -440,11 +440,9 @@ tempfile)." ;; switch on the mode (mu4e-compose-mode) (when mu4e-compose-in-new-frame - ;; make sure to close the frame when we're done with - ;; the message - ;; these are all buffer-local; + ;; make sure to close the frame when we're done with the message these are + ;; all buffer-local; (push 'delete-frame message-exit-actions) - (push 'delete-frame message-kill-actions) (push 'delete-frame message-postpone-actions))) (defun mu4e-sent-handler (docid path)