From: ludo@gnu.org (Ludovic Courtès)
To: ding@gnus.org
Subject: Re: [PATCH] Add `nnregistry', for use in `gnus-refer-article-method'
Date: Mon, 27 Sep 2010 22:57:54 +0200 [thread overview]
Message-ID: <87mxr2lx9p.fsf@gnu.org> (raw)
In-Reply-To: <87k4m76nsm.fsf@lifelogs.com>
Hi Ted,
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 10 Jul 2010 17:07:13 +0200 ludo@gnu.org (Ludovic Courtès) wrote:
>
> LC> My copyright assignment is now on file (at last), and I’d like
> LC> ‘nnregistry’ to “get in” (see the referred message). Can somebody look
> LC> into it? I still have to update the manual.
>
> Thanks for working on that. I don't think the backend interface has
> changed but maybe Lars has a comment. Have you tested it with the
> latest Gnus?
No. I’m planning to switch to No Gnus real soon but haven’t dared yet.
:-)
> LC> In addition, I think it’d be great to change the default value of
> LC> ‘gnus-refer-article-method’ to include ‘nnregistry’
>
> Is it safe if the registry is not enabled?
It calls ‘gnus-registry-fetch-group’, which should just return ‘nil’ if
the registry is not enabled (IIUC), so that should be safe.
> LC> and also change the default value of ‘gnus-registry-max-entries’ to
> LC> at least 5000.
>
> That's kind of dangerous. Searching the registry is pretty fast
> (although still O(n) unless you know the exact message-ID) but saving
> and loading it can get really slow, plus memory usage will get worse.
> So I'd make this a recommendation in the manual but not a default.
Hmm, OK.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-09-27 20:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 15:09 Using the registry for `gnus-refer-article-method' Ludovic Courtès
2009-07-31 17:44 ` Ted Zlatanov
2009-07-31 22:26 ` Ludovic Courtès
2009-08-17 15:16 ` [PATCH] Add `nnregistry', for use in `gnus-refer-article-method' Ludovic Courtès
2009-08-20 21:52 ` Ted Zlatanov
2009-08-20 23:53 ` Ludovic Courtès
2009-08-21 19:00 ` Ted Zlatanov
2009-08-21 6:47 ` Reiner Steib
2010-07-10 15:07 ` Ludovic Courtès
2010-09-27 16:28 ` Lars Magne Ingebrigtsen
2010-09-27 18:28 ` Ted Zlatanov
2010-09-27 21:01 ` Ludovic Courtès
2010-09-27 21:34 ` Ted Zlatanov
2010-09-29 14:41 ` Lars Magne Ingebrigtsen
2010-09-30 14:28 ` Ludovic Courtès
2010-09-30 15:14 ` Ted Zlatanov
2010-09-30 16:19 ` Lars Magne Ingebrigtsen
2010-09-30 22:14 ` Ted Zlatanov
2010-09-30 22:39 ` Ted Zlatanov
2010-10-01 16:27 ` Ludovic Courtès
2010-10-01 16:36 ` Ted Zlatanov
2010-10-01 22:33 ` Ludovic Courtès
2010-10-04 16:42 ` Ted Zlatanov
2010-10-05 10:05 ` Ludovic Courtès
2010-10-05 13:14 ` Ted Zlatanov
2010-10-05 14:36 ` Ludovic Courtès
2010-10-08 15:50 ` Ted Zlatanov
2010-10-11 20:20 ` Ludovic Courtès
2010-09-27 18:31 ` Ted Zlatanov
2010-09-27 18:44 ` Lars Magne Ingebrigtsen
2010-09-27 20:57 ` Ludovic Courtès [this message]
2010-09-27 21:04 ` Ted Zlatanov
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=87mxr2lx9p.fsf@gnu.org \
--to=ludo@gnu.org \
--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).