From 392610059c6aa31f609802adfa6a92e63718ab0c Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sat, 23 May 2026 03:53:23 -0500 Subject: docs(todo): close mail compose lifecycle clarification --- todo.org | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/todo.org b/todo.org index b3a29e0c..cf589269 100644 --- a/todo.org +++ b/todo.org @@ -2404,17 +2404,8 @@ Expected outcome: - Add a short manual checklist or mocked test for the variables that control remote image display. -**** TODO [#B] Clean up mail compose buffer lifecycle conflicts :cleanup:quick:solo: - -=mail-config.el= first sets =message-kill-buffer-on-exit= to =t= in the mu4e -configuration, then =org-msg= later sets it to nil. That may be intentional for -org-msg editing, but the ownership is unclear. - -Expected outcome: -- Decide whether compose buffers should be killed on send/exit for plain mu4e, - org-msg, or both. -- Move the final policy next to the owner module. -- Add a short note in the config explaining the choice. +**** 2026-05-23 Sat @ 03:52:00 -0500 Clarified message-kill-buffer-on-exit ownership +The effective policy was already settled: org-msg-mode runs in every compose buffer, so org-msg's =nil= (keep the buffer) always wins over mu4e's =t=. The org-msg comment ("always kill buffers on exit") was backwards. Rewrote both comments to name the owner: mu4e's =t= is the plain-mu4e fallback (only if org-msg is disabled), org-msg owns the live keep-the-draft policy. No behavior change — the decision the task asked for was already encoded; if Craig wants compose buffers killed on exit, flip the org-msg value. Fixed in dd671f8c. **** TODO [#B] Remove automatic startup timers from =quick-video-capture.el= :startup:refactor: -- cgit v1.2.3