Hello, Ian. On Fri, Dec 11, 2015 at 10:13:32AM -0800, Ian Zimmerman wrote: > On 2015-12-11 16:02 +0000, Alan Mackenzie wrote:
> > I have played around a little with my ~/.mailcap file (which generally > > works, e.g. for things like files.pdf), but nothing I do appears to > > have the slightest impact on these html mails. Currently, I have this > > entry for text/html: > > text/html; lynx -force_html -dump %s ; copiousoutput ; nametemplate=%s.html > > I don't believe mutt is paying any attention to this .mailcap entry. > > At one stage, I put firefox into the line in place of lynx, but this > > made no difference: the raw, unrendered mail was dumped onto my > > terminal. > vanilla mutt doesn't automatically "view" text/html MIME parts (or any > others). This is partly for the sake of security. If you want this to > happen, you can (on your own risk, of course) add an auto_view command > to your .muttrc. See the reference manual for details on syntax. I've put the auto_view into my config, and it now does indeed work. I'm willing to take the (slight) risk of some nasty getting in: I'm relying on the -dump argument to lynx preventing me interacting in any way with the html. Thanks! I think it's fair to say the manual is less helpful here than it might be. In the .mailcap section it gives several examples of using lynx for text/html without once mentioning the need for an auto_view command. -- Alan Mackenzie (Nuremberg, Germany).
