From: Romain Francoise <romain@orebokech.com>
Cc: ding@gnus.org
Subject: Re: Changes committed gnus/contrib (ChangeLog compface.el)
Date: Sun, 24 Oct 2004 18:13:54 +0200 [thread overview]
Message-ID: <87pt38um9p.fsf@orebokech.com> (raw)
In-Reply-To: <E1CHV1v-00031P-00@quimby.gnus.org> (Katsumi Yamaoka's message of "Wed, 13 Oct 2004 00:22:03 +0200")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Move the version of ELisp-based uncompface program from the lisp directory
> because of the copyright problem.
This is problematic since (unless I missed something) files in contrib/
are not automatically byte-compiled. I upgraded my No Gnus copy and was
surprised to see that articles with X-Face headers were rendered _very_
slowly[1] on my not so slow system... Byte-compiling compface.el fixed
the problem, rendering is instantaneous again.
Would it be a good idea to byte-compile files in contrib as well?
--
Romain Francoise <romain@orebokech.com> | You know that old saying,
it's a miracle -- http://orebokech.com/ | that you always hurt the ones
| you love? Well it works both
| ways.
Footnotes:
[1] ELP results:
Function Name Call Count Elapsed Time Average Time
====================== ========== ============ ============
uncompface 1 1.495175 1.495175
uncompface-internal 1 1.495155 1.495155
uncompface-uncompress 241 0.1217170000 0.0005050497
uncompface-big-mul-add 408 0.031415 7.699...e-05
uncompface-big-pop 319 0.0303899999 9.526...e-05
uncompface-pop-grays 83 0.0130459999 0.0001571807
next parent reply other threads:[~2004-10-24 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CHV1v-00031P-00@quimby.gnus.org>
2004-10-24 16:13 ` Romain Francoise [this message]
2004-10-24 23:51 ` Katsumi Yamaoka
2004-10-25 6:19 ` Romain Francoise
2004-10-25 7:21 ` Katsumi Yamaoka
2006-04-15 13:27 ` 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=87pt38um9p.fsf@orebokech.com \
--to=romain@orebokech.com \
--cc=ding@gnus.org \
/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).