Thanks for all the advice. On Sat, Oct 30, 2021 at 04:13:31PM -0400, Hendrik Boom wrote: > Until upgraded from ascii to beowulf, HTML messages were tolerable. > Either they were obvious crap, in which case I just deeted them, > or they seemed like they were worth viewing, in which case they were > usually html attachments, and I could seen the list of attachments by > typeing v and selecting the html version -- in which case it would > open for me in the chromium browser. > > This stopped working after the upgrade to beowulf. > > I did manage to reconfigure, telling it to use firefox-esr, but that > didn't help much. I connect to my server, the machine on which I run > mutt, using ssh -X. > So firefox on the server detects I already have a firefox browser > on my laptop and proceeds to give the job of browsing the message to > my laptop. > Makes sense, except that my laptop has no way to access the > /tmp/mutt/somethingorother.html on the server. > > And I have not been able to get mutt to call chromium at all. > > Any ideas?
By tring things that were suggested, and trying to make sense of the documentation slightly more informed than random, I managed to get firefox to display html contents from the server where the files are. ~/.muttrc: set mailcap_path="~/.mailcap" auto_view text/html bind pager Q exit subscribe racket-us...@googlegroups.com ~/.mailcap: #text/html ; chromium %s text/html ; firefox-esr -no-remote %s ; copiousoutput Unfortunately it now prefers the .html version to the plaintext version. I presume I need an alternative_order line. -- hendrik _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
