From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: ELisp-based uncompface
Date: Mon, 16 Feb 2004 15:04:25 +0100 [thread overview]
Message-ID: <v98yj33yty.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3isicu9l6.fsf@defun.localdomain>
On Thu, Feb 12 2004, Jesper Harder wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> It's fast enough for me too, however I heard it takes seconds
>> per image in the slow machine.
>
> It takes around 0.3 s (versus 0.03 s for the external decoder) on my
> 233 MHz pentium box, which I think is a rather low-end machine by
> today's standards.
>
> It's not used in a loop, so don't think many will notice any
> difference even on a slow machine.
Hm, the delay is notable on my P200 and P266 I'm using at home. (I
didn't benchmark it, though.)
Is there a (portable) way in lisp to find out if the machine is slow?
Maybe it's enough to mention `uncompface-use-external' in (info
"(gnus)Slow Machine").
If we just want to provide support for installations missing the
external "uncompface" (this was the initial motivation, if I
understood correctly), we could use something like this:
(defcustom uncompface-use-external (and (executable-find "uncompface")
(executable-find "icontopbm")
t)
[...])
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-02-16 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 0:46 Katsumi Yamaoka
2004-02-12 3:19 ` Jesper Harder
2004-02-12 4:21 ` Katsumi Yamaoka
2004-02-12 5:53 ` Jesper Harder
2004-02-12 6:05 ` Katsumi Yamaoka
2004-02-16 14:04 ` Reiner Steib [this message]
2004-02-17 5:59 ` Katsumi Yamaoka
2004-02-18 15:47 ` Reiner Steib
2004-02-18 17:23 ` Ted Zlatanov
2004-02-18 23:00 ` Katsumi Yamaoka
2004-02-13 16:25 ` Xavier Maillard
2004-10-11 23:19 ` Katsumi Yamaoka
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=v98yj33yty.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).