From faade24945551a2513d93820142e88f1d44a6732 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Thu, 11 Apr 2024 20:02:01 +0300 Subject: [PATCH] mu4e-compose: kill fcc buffer after sending There's a buried buffer for the fcc file... not quite sure why, but let's kill it after we've sent the message. Fixes #2681. --- mu4e/mu4e-compose.el | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/mu4e/mu4e-compose.el b/mu4e/mu4e-compose.el index ca5329ae..523ac88c 100644 --- a/mu4e/mu4e-compose.el +++ b/mu4e/mu4e-compose.el @@ -560,7 +560,13 @@ appropriate flag at the message forwarded or replied-to." ;; appropriate flag at the message forwarded or replied-to. (add-hook 'message-sent-hook (lambda () - (mu4e--set-parent-flags fcc-path)) nil t)))) + (mu4e--set-parent-flags fcc-path) + ;; we end up with a ((buried) buffer here, visiting + ;; the fcc-path; not quite sure why. But let's + ;; get rid of it (#2681) + (when-let ((buf (find-buffer-visiting fcc-path))) + (kill-buffer buf))) + nil t)))) ;;; Crypto (defun mu4e--compose-setup-crypto (parent compose-type)