Re: nnir, gnus-goto-article and such

[Dave Abrahams <dave@boostpro.com>]

on Thu Sep 29 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:

> On Wed, 28 Sep 2011 22:06:37 -0400 Dave Abrahams <dave@boostpro.com> wrote: 
>
> DA> So, thanks, you seem to have gotten me over one hump... here's my patch:
> DA> 	Modified   lisp/gnus-sum.el
> DA> diff --git a/lisp/gnus-sum.el b/lisp/gnus-sum.el
> DA> index 423de35..8452bb9 100644
> DA> --- a/lisp/gnus-sum.el
> DA> +++ b/lisp/gnus-sum.el
> DA> @@ -9077,6 +9077,13 @@ non-numeric or nil fetch the number specified by the
> DA>  		       (setq number (gnus-summary-insert-subject message-id)))
> DA>  	      ;; and display the article.
> DA>  	      (gnus-summary-select-article nil nil nil number)
> DA> +              (when (bound-and-true-p gnus-registry-install)
> DA> +                (let ((header (gnus-summary-article-header (gnus-summary-article-number))))
> DA> +                  (gnus-registry-handle-action
> DA> +                   message-id nil
> DA> +                   (gnus-method-to-full-server-name gnus-override-method)
> DA> +                   (mail-header-subject header)
> DA> +                   (mail-header-from header))))
> DA>  	      (throw 'found t)))
> DA>  	  (gnus-message 3 "Couldn't fetch article %s" message-id)))))))
>
> DA> But now, of course, gnus-warp-to-article doesn't consult the registry to
> DA> find out the article's group, so `A T' still fails.  For some reason, it
> DA> goes directly to the backend, only one of which supports warping: nnir.
>
> I think you need to explicitly enable nnregistry so that will work (see
> the comments).  

in nnregistry.el there are no comments.

in gnus-registry.el it says

  ;; You should also consider using the nnregistry backend to look up
  ;; articles.  See the Gnus manual for more information.

The Gnus manual says almost nothing useful about nnregistry.  It shows
how it can be used in gnus-refer-article-method, and I have done that.

What further enabling do you have in mind?

> Perhaps it should be automatically loaded when the Gnus registry is
> initialized.  Andy Cohen did that work IIRC so I don't know if there
> are any reasons not to do it.  It seems reasonable to me.
>
> DA> [Aside: it seems like this territory is full of components that
> DA> could in principle be nicely generalized, but whose implementation
> DA> has only been made to work for one specific usage scenario]
>
> I can't tell, I was not involved with writing these components.  

IIUC from reading elsewhere you rewrote the registry.

> At least for the registry I know it's optional so we can't depend on
> it.

I'm not sure what "optional" means in this context.  Is Gnus going to
ship without the registry code?

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com