alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e: don't use message-kill-actions for closing frames

Browse Source 
Seems it is handled by the other actions already, and kills one-too-many
frames.
This commit is contained in:
djcb
2016-02-21 16:33:55 +02:00
parent 24194b4d12
commit 2b0d75b295
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
mu4e/mu4e-compose.el
View File

@ -440,11 +440,9 @@ tempfile)."
;; switch on the mode ;; switch on the mode
(mu4e-compose-mode) (mu4e-compose-mode)
(when mu4e-compose-in-new-frame (when mu4e-compose-in-new-frame
;; make sure to close the frame when we're done with ;; make sure to close the frame when we're done with the message these are
;; the message ;; all buffer-local;
;; these are all buffer-local;
(push 'delete-frame message-exit-actions) (push 'delete-frame message-exit-actions)
(push 'delete-frame message-kill-actions)
(push 'delete-frame message-postpone-actions))) (push 'delete-frame message-postpone-actions)))
(defun mu4e-sent-handler (docid path) (defun mu4e-sent-handler (docid path)