From: ludo@gnu.org (Ludovic Courtès)
To: ding@gnus.org
Subject: Re: [PATCH] Add `nnregistry', for use in `gnus-refer-article-method'
Date: Tue, 05 Oct 2010 16:36:48 +0200 [thread overview]
Message-ID: <87wrpwyadb.fsf@gnu.org> (raw)
In-Reply-To: <87tyl0n5mb.fsf@lifelogs.com>
Hi Ted!
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 05 Oct 2010 12:05:48 +0200 ludo@gnu.org (Ludovic Courtès) wrote:
>
> LC> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>>> On Sat, 02 Oct 2010 00:33:29 +0200 ludo@gnu.org (Ludovic Courtès) wrote:
>>>
> LC> Hmm, I’m not convinced by ‘gnus-registry-install-nnregistry’ because:
>>>
> LC> 1. it does things under the hood;
>>>
>>> Where else would it operate? Do you mean that every user should
>>> customize gnus-refer-article-method themselves?
>
> LC> Yes. Personally I prefer setting the variable once for all, so it’s
> LC> purely declarative and clearer (to me).
>
> OK. Do your docs include the instructions to do that?
Yes, the example explains this:
--8<---------------cut here---------------start------------->8---
(setq gnus-refer-article-method
'(current
(nnregistry)
(nnweb "gmane" (nnweb-type gmane))))
--8<---------------cut here---------------end--------------->8---
> LC> 2. it /appends/ ‘nnregistry’ to ‘gnus-refer-article-method’, whereas
> LC> it’s likely to perform better if it appears right after ‘current’.
>>>
>>> For the vast majority of Gnus users the two are the same.
>
> LC> It depends. For instance, I have ‘(nnweb "gmane" (nnweb-type gmane))’
> LC> as the last resort, which is presumably slower than nnregistry.
>
> You are unusual.
Well yes, otherwise I wouldn’t be using Gnus in the first place. :-)
> The vast majority of Gnus users don't customize or even know about
> `gnus-refer-article-method'. But it doesn't matter since we're
> removing this anyhow. Just mention it in the docs if you haven't
> already (I haven't reviewed your patch, sorry!)
The doc patch I posted should be OK, let me know what you think.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-10-05 14:36 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 [this message]
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
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=87wrpwyadb.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).