Date: Thu, 7 Oct 2010 06:51:38 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Bob Willcox <bob@immure.com> Cc: freebsd-ports@freebsd.org Subject: Re: New mutt-devel problems with text/html processing Message-ID: <20101007135138.GA81306@icarus.home.lan> In-Reply-To: <20101007132209.GA47648@rancor.immure.com> References: <20101007132209.GA47648@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote: > The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx > when it encounters a text/html file type. Instead it simply displays the raw > html text. According to their UPDATING file, they say: > > "all text/* parts can be displayed inline without mailcap" > > Which is suspiciously in the realm of the problem I'm seeing. > > Perhaps there's now some other way of displaying text/html files w/o mailcap > and an external program that I'm missing? Looks relevant, with a response from Michael Elkins explaining the change: http://marc.info/?t=128477093300004&r=1&w=2 Basically, it appears that as of 1.5.21, mutt only displays text/* MIME types using its own internal engine. If you want the old behaviour, when selecting the attachment/entry, press "m". Personally I don't like this change, but I'll deal with it. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101007135138.GA81306>