Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Inefficiency in mm-uu.el
Date: 29 Nov 1998 04:26:20 -0500	[thread overview]
Message-ID: <2n4sri4zpf.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: Hrvoje Niksic's message of "27 Nov 1998 17:17:59 +0100"

>>>>> "HN" == Hrvoje Niksic <hniksic@srce.hr> writes:

HN> The uuencode interface to mm seems very inefficient, because of
HN> two separate reasons.  When I `g' a message containing a, say, an
HN> uuencoded image, it insists on decoding the uuencoded region (I
HN> can tell by the time `g' takes and by the conducted profiles.)

HN> When I click on the image button to show it, it decodes it again.
HN> Why this double encoding?

The first decoding is due to mm-inlinable-p. With the attached patch,
each type is tested at most once in a session.

HN> The other question is about the strange default -- the code
HN> defaults to using the internal, elisp-based decoding, even when a
HN> perfectly valid `uudecode' is found on the system.  This makes
HN> decoding of large stuff (and uuencoded stuff is large, more often
HN> than not) abysmally slow, even on very very fast machines.  I can
HN> imagine that on slower machines it's closer to "unusable".

Do you mean to automatically setup mm-uu-decode-function by searching
uudecode on the system at loading time of mm-uu.el?  If so, please
feel free to patch it.

-- 
Shenghuo

:- cut -----
--- ChangeLog	1998/11/29 08:49:39	1.1
+++ ChangeLog	1998/11/29 08:51:02
@@ -1,3 +1,7 @@
+Sun Nov 29 03:50:20 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>
+
+	* mm-decode.el (mm-inlinable-p): Save the result of test.
+
 Fri Nov 27 12:26:10 1998  Lars Magne Ingebrigtsen  <larsi@menja.ifi.uio.no>
 
 	* gnus.el: Pterodactyl Gnus v0.55 is released.

--- mm-decode.el	1998/11/29 08:44:18	1.1
+++ mm-decode.el	1998/11/29 08:47:55
@@ -357,9 +357,11 @@
 	test)
     (while alist
       (when (equal type (caar alist))
-	(setq test (caddar alist)
-	      alist nil)
-	(setq test (eval test)))
+	(setq test (caddar alist))
+	(when (consp test)
+	  (setq test (eval test))
+	  (setf (caddar alist) test))
+	(setq alist nil))
       (pop alist))
     test))
 


       reply	other threads:[~1998-11-29  9:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <kigaf1d3ya0.fsf@jagor.srce.hr>
1998-11-29  9:26 ` Shenghuo ZHU [this message]
1998-11-29 14:44   ` Hrvoje Niksic
1998-11-29 21:37     ` Lars Magne Ingebrigtsen
1998-11-29 23:06       ` Hrvoje Niksic
1998-11-30 13:59       ` Jan Vroonhof
1998-11-30 14:29         ` Steinar Bang
1998-11-30 14:41           ` Jean-Yves Perrier
1998-11-30 17:15           ` Jan Vroonhof
1998-11-29 21:31   ` Lars Magne Ingebrigtsen
1998-11-29 23:08     ` Hrvoje Niksic
1998-11-30  2:46       ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2n4sri4zpf.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).