Date: Fri, 8 Oct 2010 07:49:49 -0500 From: Bob Willcox <bob@immure.com> To: Anton Shterenlikht <mexas@bristol.ac.uk> Cc: freebsd-ports@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: New mutt-devel problems with text/html processing Message-ID: <20101008124949.GA54088@rancor.immure.com> In-Reply-To: <20101008083107.GA80449@mech-cluster241.men.bris.ac.uk> References: <20101007132209.GA47648@rancor.immure.com> <20101007135138.GA81306@icarus.home.lan> <20101007162243.GA48756@rancor.immure.com> <20101008083107.GA80449@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 08, 2010 at 09:31:08AM +0100, Anton Shterenlikht wrote: > On Thu, Oct 07, 2010 at 11:26:06AM -0500, Bob Willcox wrote: > > On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote: > > > 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. > > > > Thanks Jeremy, that was it. Guess I'll just have to get used to pressing 'm' > > now. > > I missed the beginning of this thread. I had mutt-devel until > about a week ago, when, after some update, it became extremely > slow. For example, using just /var/mail it would take 10 seconds > or more to move from one message to another in index. The same > delay for opening messages in pager. The size of messages was > same as before, mostly 2-3 lines with occasional attachment. > > Anyway, I rolled back to mutt-1.4.2.3_5, which works fine. > > This has probably nothing to do with the Subject, just > thought perhaps somebody else seen a significant slow down > after the update? I haven't seen this behavior. My only issue was the change in how the latest mutt-devel handles text/* type attachements. I've seen no change in performance. Bob > > many thanks > anton > Sorry if this has nothin > > > > Bob > > > > > > > > -- > > > | 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 | > > > > -- > > Bob Willcox A great many people think they are thinking > > bob@immure.com when they are merely rearranging their prejudices. > > Austin, TX -- William James > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 -- Bob Willcox A great many people think they are thinking bob@immure.com when they are merely rearranging their prejudices. Austin, TX -- William James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101008124949.GA54088>