David Bremner writes:
> That makes sense to me, with the (perhaps obvious) caveat that calling
> without binding the setup function should cleanly do the display
> (perhaps with less fontification) and return.
Yup. I've now done the refactoring, so there should be no user-visible
changes for Gn
Lars Ingebrigtsen writes:
> But perhaps the function should be rewritten to call a (say)
> `mm-inline-message-setup-function', bound by the caller? Then both Gnus
> and notmuch could use the function.
That makes sense to me, with the (perhaps obvious) caveat that calling
without binding the set
David Bremner writes:
> I should have been more precise. I'm calling it indirectly via
> mm-display-part, which is useful in the case where someone attaches a
> message/rfc822 part to their message. In principle notmuch can (and in
> the general case does) render the part directly, but in certain
Lars Ingebrigtsen writes:
>
> Yeah, it's confusing. `mm-inline-message' is really an "internal" Gnus
> function, while most of the other mm functions are more general.
>
> Disentangling that mess is daunting, but for that function in
> particular, I guess it wouldn't be that difficult to rewrite
David Bremner writes:
> notmuch-show-mode relies on various mm-* functions to display message
> parts. This is problematic for "message/rfc822" parts, since
> mm-inline-message ends up calling (gnus-article-prepare-display) which
> resets the buffer major-mode to gnus-article-mode since
> notmuch
