This is a great post about a very finely tuned Mutt setup. I always enjoy reading about high customized environments. I am someone who would love to use Mutt but I get so much HTML only email it's sadly impossible for me to do so. (Newsletters and misc friends who think large HTML footers are cool.)
Comments
This is a great post about a very finely tuned Mutt setup. I always enjoy reading about high customized environments. I am someone who would love to use Mutt but I get so much HTML only email it's sadly impossible for me to do so. (Newsletters and misc friends who think large HTML footers are cool.)
In your .muttrc:
auto_view text/html alternative_order text/plain text text/html
That presents plain text first if it's multiply-encoded, but makes html available. In your mailcap:
text/html; /path/to/browser '%s'; description=HTML Text; test=test -n "$DISPLAY"; nametemplate=%s.html
displays HTML in a browser window for you. mutt launches this when you choose to look at the html version.
But instead, your mailcap could have this:
text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
which mutt interprets as "filter this through lynx and display it in the terminal" which will solve 98% of your issues. It's fast, too.
I'll give lynx a try with this, I can't use a full browser as it would be on a remote computer setup. Thanks for the tip!
Super awesome! I use mutt on a remote server and don't want a browser involved. This recipe really does a nice job.