control: retitle 823971 mutt: displays text/html raw instead of using mailcap
Eduard Bloch schrob: > same here, the ability to read inline HTML parts without ugly > workarounds is really missed. There are two easy workarounds. The first is using "m". Quoting TFM, Table 9.7. Default Attachment Menu Bindings: <view-mailcap> m force viewing of attachment using mailcap <view-text> T view attachment as text <view-attach> <Return> view attachment using mailcap entry if necessary The second is setting "auto_view text/html" in your .muttrc , which causes a rendered version of the html to be displayed instead of the raw source. HTH. However, I still prefer the previous behaviour of, by default, spawning an interactive browser for text/html. Thus I recompiled mutt 1.6.0-1 with 611410-no-implicit_autoview-for-text-html.patch , and can confirm it builds cleanly and fixes this issue. The patch was dropped due to dbug #816706, where Kevin McCarthy claims Fixed in https://dev.mutt.org/trac/ticket/3496 3 years ago. Unfortunately, that ticket seems to have considered only (implicit)autoview functionality, i.e. the question whether mutt displays the raw html or the text result of a mime rule like text/html; /usr/bin/elinks -force-html -dump %s; copiousoutput; ... The debian patch goes beyond that in providing the (default) behaviour of actually opening the html in a browser via a rule like text/html; /usr/bin/elinks -force-html %s; needsterminal; ... Please consider reinstating the patch. Thanks, Jan
signature.asc
Description: PGP signature