From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: (gnus-summary-goto-article <message-id>) extremely slow for certain IMAP server
Date: Mon, 26 Jul 2010 16:08:54 -0500 [thread overview]
Message-ID: <87iq42x861.fsf@lifelogs.com> (raw)
In-Reply-To: <201007262143.28216.tassilo@member.fsf.org>
On Mon, 26 Jul 2010 21:43:02 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote:
TH> On Monday 26 July 2010 21:27:13 David Engster wrote:
>> Yes. An IMAP server should be able to retrieve articles based on
>> message-id's very quickly, since this is a pretty common task.
TH> That's my impression, too. But at least Sébastiens Courier server seems
TH> to think otherwise. Maybe it's only some config option the admins need
TH> to enable, who knows...
I use Courier and it's pretty fast for message-id searches. Perhaps
Sébastien can run a local IMAP synced server?
>> > Or can this call to `imap-search' somehow be omitted by optional
>> > Gnus features like the gnus registry?
>>
>> Probably, but currently the registry does not keep track of the
>> article numbers, only of the groups. I guess this could easily be
>> added, though?
Yes, but it wouldn't help for IMAP. IMAP article numbers are too
mutable. The registry tries to be above the backend level and article
numbers are too close to that level. But it's not hard at all to add
extra data of any type; see gnus-registry-fetch-extra-entry and
gnus-registry-store-extra-entry. The registry marks use those functions.
On Mon, 26 Jul 2010 22:29:12 +0200 David Engster <deng@randomsample.de> wrote:
DE> (nth 1 (gnus-find-method-for-group group))
I think (gnus-method-to-server-name (gnus-find-method-for-group group))
is a little better.
Ted
next prev parent reply other threads:[~2010-07-26 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 18:42 Tassilo Horn
2010-07-26 19:27 ` David Engster
2010-07-26 19:43 ` Tassilo Horn
2010-07-26 20:29 ` David Engster
2010-07-26 21:08 ` Ted Zlatanov [this message]
2010-07-26 21:29 ` David Engster
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=87iq42x861.fsf@lifelogs.com \
--to=tzz@lifelogs.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).