From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
To: "Bjørn Mork" <bmork@dod.no>
Cc: ding@gnus.org
Subject: Re: Unnecessary hashcash computations
Date: Thu, 08 Mar 2007 22:54:14 +0100 [thread overview]
Message-ID: <87bqj3s8op.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <87bqjv8whn.fsf@obelix.mork.no> (=?iso-8859-1?Q?Bj=F8rn?= Mork's message of "Thu\, 15 Feb 2007 12\:56\:52 +0100")
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Bjørn Mork writes:
> Does anyone see how this could be avoided, still keeping the async
> computation? If we at the same time could get async hashcash
> computation for new recepients, then that would of course be even
> better.
I don't have a solution for the former, but I have the following in my
.gnus.el to take care of the latter:
[-- Attachment #2: Type: application/emacs-lisp, Size: 302 bytes --]
[-- Attachment #3: Type: text/plain, Size: 223 bytes --]
However, I'm not sure what the canonical way to integrate this into
Gnus would be. Introducing a message-goto-body-hook might be more
general, but this wouldn't allow for the prefix arg to be specified.
regards,
andreas
prev parent reply other threads:[~2007-03-08 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:56 Bjørn Mork
2007-03-08 21:54 ` Andreas Seltenreich [this message]
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=87bqj3s8op.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.org \
--cc=bmork@dod.no \
--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).