<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dotemacs/docs/mu4e-org-msg-compose-buffer-cleanup.org, branch main</title>
<subtitle>My Emacs configuration
</subtitle>
<id>https://git.cjennings.net/dotemacs/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/dotemacs/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/'/>
<updated>2026-05-23T09:10:58+00:00</updated>
<entry>
<title>docs(mail): document compose-buffer cleanup settings</title>
<updated>2026-05-23T09:10:58+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-23T09:10:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/commit/?id=c7fa570bbed7a40c3531fda0eb410419873bb1a6'/>
<id>urn:sha1:c7fa570bbed7a40c3531fda0eb410419873bb1a6</id>
<content type='text'>
I added docs/mu4e-org-msg-compose-buffer-cleanup.org explaining the one setting that controls whether mail compose buffers close on exit (message-kill-buffer-on-exit), why org-msg needs no setting of its own (it reads the variable, never sets it), and the trap that a stray setter in org-msg's :config silently wins over the mu4e one.
</content>
</entry>
</feed>
