From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Subject: Re: why does message-generate-headers take so long?
Date: Wed, 23 Aug 2006 06:24:42 +0200 [thread overview]
Message-ID: <87sljorsdx.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <lsphd04mlzf.fsf@saturna.ca.boeing.com> (Ted Stern's message of "Tue, 22 Aug 2006 15:41:56 -0700")
Ted Stern <dodecatheon@gmail.com> writes:
> Can anyone think of a reason why that routine would take so long?
Hashcash.
> Why is it being called twice?
IIRC message conses up a scratch message buffer, but hashcash
generation is inhibited for this one.
> Is there any way to speed it up?
--8<---------------cut here---------------start------------->8---
message-generate-hashcash is a variable defined in `message.el'.
Its value is t
Documentation:
*Whether to generate X-Hashcash: headers.
You must have the "hashcash" binary installed, see `hashcash-path'.
You can customize this variable.
--8<---------------cut here---------------end--------------->8---
regards,
andreas
next prev parent reply other threads:[~2006-08-23 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 22:41 Ted Stern
2006-08-23 4:24 ` Andreas Seltenreich [this message]
2006-08-23 8:43 ` Simon Josefsson
2006-08-23 13:47 ` Wes Hardaker
2006-08-23 15:15 ` Simon Josefsson
2006-08-23 15:34 ` gdt
2006-08-23 8:34 ` Elias Oltmanns
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=87sljorsdx.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.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).