Re: nnir, gnus-goto-article and such

[Dave Abrahams <dave@boostpro.com>]

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

> On Tue, 27 Sep 2011 11:35:42 -0400 Dave Abrahams <dave@boostpro.com> wrote: 
>
> DA> on Mon Sep 26 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
>
>>> The registry is a place where we record interesting things (group,
>>> subject, sender, recipients, registry marks) about articles, keyed by
>>> the message ID.  But it's also a general key-val store with some
>>> indexing.  For Lars' point, the registry is an opportunistic cache that
>>> remember where you've seen a message-ID (server name and group name) and
>>> where it's been split before.
>
> DA> Yes, I understand all that... I know what it is as a library component.
> DA> What I don't see is how *at the user level* it can easily and usefully
> DA> be exploited.
>
> Er, you can split to the reference parent, 

I don't use client-side splitting, so I guess that doesn't make much
difference to me, but I guess it might for others.

> or by subject, or by sender?  

You can't split by subject or sender without the registry?!  You're
kidding, right?  Like I said, I never ask Gnus to shuffle mail into
different folders for me but that seems pretty basic.

> It lets the user keep registry marks?  Are those not exploitative
> enough?

What's a user going to *do* with registry marks?  That's another tool
whose real utility escapes me.

>>> Simply call it like this (for message-ID "34"):
>>> 
>>> (gnus-registry-get-id-key "34" 'group)
>>> (gnus-registry-get-id-key "34" 'subject)
>
> DA> "34" sounds like a message number, not a Message-ID (like what's found
> DA> in mail headers).  How is gnus-registry going to know which group's
> DA> number 34 I'm referencing?
>
> No, I said message-ID was 34 so I didn't have to type
> "<m2wrcu0zht.fsf@pluto.luannocracy.com>".  Sorry for the confusion.

np, thanks for the clarification.

> DA> So here's an example where I tried it out.  
>
> DA> (defun gnus-goto-article (message-id)
> DA>   (with-temp-buffer
> DA>     (erase-buffer)
> DA>     ;; Insert dummy article
> DA>     (insert (format "From nobody Tue Sep 13 22:05:34 2011\n\n"))
> DA>     (gnus-group-read-ephemeral-group message-id
> DA>      `(nndoc ,message-id
> DA>              (nndoc-address ,(current-buffer))
> DA>              (nndoc-article-type mbox))
> DA>      'activate
> DA>      (not    'quit-config)
> DA>      (not    'request-only)
> DA>      '(-1) ; 'select-articles
> DA>      (not    'parameters)
> DA>      0     ; ' number
> DA>      )
> DA>     (gnus-summary-refer-article message-id)
> DA>     (message "group from registry: %s" (gnus-registry-get-id-key message-id 'group))
> DA>     ))
>
> DA> I queried the registry at the point where I'd like to know the group of
> DA> that article.  Unfortunately, I get back nil.  And if I wanted to
> DA> conjure up an article number, well, it's -1, so that's not going to be
> DA> much help, is it?
>
> The registry notices articles when you visit a group or when articles
> are split.  To feed it artificial data, use:
>
> (defun gnus-registry-handle-action (id from to subject sender
>                                        &optional recipients)

Umm, sorry.  That function isn't documented.  How do I use it?  How
would I get the group that gnus-summary-refer-article finds the message
in into the registry?  I don't even see a parameter for group.

> I hope that helps...

Getting there, but not quite yet.

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