diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-23 03:53:10 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-23 03:53:10 -0500 |
| commit | ab04450d127ff625fd11d135f1282b6858665558 (patch) | |
| tree | 4bc803a2f9ddb882c3b7b8fd6bb5d6597ea00b1b /scripts/calendar_sync_api.py | |
| parent | f2c7cd50897ba2ddb6eb6dd64d7f8a447a3ff3b0 (diff) | |
| download | dotemacs-ab04450d127ff625fd11d135f1282b6858665558.tar.gz dotemacs-ab04450d127ff625fd11d135f1282b6858665558.zip | |
docs(mail): clarify message-kill-buffer-on-exit ownership
mail-config.el set message-kill-buffer-on-exit to t in mu4e's config and nil in org-msg's, with no note on which wins. org-msg-mode runs in every compose buffer, so org-msg's nil is the effective policy: compose buffers are kept, not killed. The org-msg comment said "always kill buffers on exit", which is backwards.
I rewrote both comments. The mu4e t is the plain-mu4e fallback that only matters if org-msg is ever disabled, and org-msg owns the live policy of keeping a draft buffer on exit so an in-progress HTML message isn't lost. No behavior change.
Diffstat (limited to 'scripts/calendar_sync_api.py')
0 files changed, 0 insertions, 0 deletions