On 12/11/16 00:20, David Bremner wrote: > Matthew Lear <matt@bubblegen.co.uk> writes: > >> I can trigger the bug if I discard text/plain though. Did you try that? > > I'm not sure what you mean by "discard", but closing it isn't enough. I > think more of your settings are needed to replicate the problem with a > multipart/alternative message. > Apologies, David. I wasn't clear at all. I meant that if I discourage text/plain in a multipart/alternative message, I can trigger the bug. If I use the following tiny-init.el... (require 'shr) (setq mm-text-html-renderer 'shr) (setq mime-view-text/html-previewer 'shr) (setq mm-html-inhibit-images nil) (setq mm-html-blocked-images nil) (require 'notmuch) (global-set-key [f1] 'notmuch) (setq notmuch-mua-compose-in 'new-frame) (setq notmuch-multipart/alternative-discouraged '("text/plain")) ...and load it using 'emacs-25 -q --load ~/.emacs.d/tiny-init.el', searching for any mimetype:text/html and replying to it triggers the bug for me. Commenting out the setting of notmuch-mua-compose-in is enough to prevent the problem from occurring. Cheers, -- Matt