> Regarding the following, written by "Derek Martin" on 2019-10-31 at 15:39 Uhr > -0500: > > And FWIW, I *was* discussing (very limited, completely text-based) > > support for HTML messages in Mutt. I want it, have wanted it for a long > > time, because all of the available options for dealing with it have > > serious drawbacks at least some of the time.
martin f krafft writes: > Could you please elaborate a bit on what you're missing? > > With `auto_view text/html` and adding > [`~/.mutt/mailcap.htmldump`](https://git.madduck.net/etc/mutt.git/blob_plain/HEAD:/.mutt/mailcap.htmldump) > to your `muttrc`'s `mailcap_path` setting, and then dropping > [`~/.mutt/htmldump`](https://git.madduck.net/etc/mutt.git/blob_plain/HEAD:/.mutt/htmldump) > in place, along with > [`python-html2text`](https://pypi.org/project/html2text/), and you should > get Markdown, more or less, which is precisely what it was designed for. That sounds like it's all on the viewing side? I can't speak for Derek, but in addition to viewing HTML messages, I (and others who have added to this thread) would like a way to reply without losing the formatting. The viewing side isn't so hot either. Most terminal programs these days can display colors, italics, bold, underline and strikethrough (looks like urxvt doesn't do strikethrough and xterm doesn't do underline, but those might not be too hard to patch in). So why do most HTML->text conversion programs ignore styles and colors in --dump mode? Is there one that shows styles/colors? Sure, it's easy enough to bind a key to bring up a browser window showing the message. But then I have an extra GUI window that isn't part of mutt, and it breaks that nice fast keyboard-driven workflow that's a big part of why I use mutt in the first place. It would be so nice to have it all right there in the pager. ...Akkana
