Regarding the following, written by “John Long” on 2019-10-30 at 11:31 Uhr +0000:

From my point the issue is not only what I have to configure or what can be configured, but also how much code is behind doing that. Less code is easier to manage than more code. I can’t see the benefit of junking up mutt with HTML …

Fully agreed on all of the above.

The approach Kevin proposed is completely HTML-agnostic and leaves it up to the user to provide an external tool that provides the HTML. Mutt then just does the required MIME-handling, which is clearly within the domain of a MUA.

Also, mutt already does receiving/reading multipart/alternative, so it only makes sense to figure out how to properly add creation of such containers. After all, mutt can sign GPG signatures, not just verify them.

Remember, some of us use mutt on a console with no GUI.

There is no GUI requirement in any of this.

@martinkrafft |

"all i know is that i'm being sued for unfair business
practices by micro$oft. hello pot? it's kettle on line two."
-- michael robertson


Reply via email to