Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH] Add `nnregistry', for use in `gnus-refer-article-method'
Date: Thu, 30 Sep 2010 17:39:42 -0500	[thread overview]
Message-ID: <8739sq500h.fsf@lifelogs.com> (raw)
In-Reply-To: <877hi2515y.fsf@lifelogs.com>

On Thu, 30 Sep 2010 17:14:49 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Thu, 30 Sep 2010 18:19:36 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
LC> What about adding ‘nnregistry’ to the default value of
LC> ‘gnus-refer-article-method’?
>>> 
>>> Maybe `gnus-registry-initialize' should do that?

LMI> Sounds reasonable.

TZ> I think it's done properly now.  But nnregistry needs to be loaded
TZ> first.  Hmm.

OK, so my best recommendation is to say

;; Put this in your startup file (~/.gnus.el for instance)

;; (require 'nnregistry) ;; optional
;; (setq gnus-registry-max-entries 2500
;;       gnus-registry-use-long-group-names t)

;; (gnus-registry-initialize)

in the gnus-registry header.  WDYT?

LMI> And nnregistry should be documented in gnus.texi.

TZ> Ludovic?

Probably it should be in the gnus-registry section of the manual (with a
minimal link elsewhere), explaining that it has to be loaded *after*
gnus-registry.el but *before* gnus-registry-initialize is called.

Ted




  reply	other threads:[~2010-09-30 22:39 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 [this message]
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
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=8739sq500h.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).