From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: nnir, gnus-goto-article and such
Date: Tue, 27 Sep 2011 11:35:42 -0400 [thread overview]
Message-ID: <m2wrcu0zht.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87pqinvvg4.fsf@lifelogs.com>
on Mon Sep 26 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
> On Mon, 26 Sep 2011 16:01:52 -0400 Dave Abrahams <dave@boostpro.com> wrote:
>
> DA> on Wed Sep 21 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
>
>>> Dave Abrahams <dave@boostpro.com> writes:
>>>
>>>> 2. (important) I'd like to see the whole thread (e.g. with `A T'). That
>>>> works fine if it's an IMAP article because nnir finds it. However,
>>>> nnir doesn't work on nntp newsgroups.
>>>>
>>>> It seems to me what's missing is some way of recording the source of
>>>> the message retrieved by gnus-summary-refer-article, and some way of
>>>> asking for a thread search in an nntp server. Ideas?
>>>
>>> Hm... `gnus-summary-refer-article' work presumably because of the
>>> registry, I guess?
>
> DA> Well, as far as I know I don't have the registry turned on and I have
> DA> never been able to understand exactly how it could help me. On the
> DA> surface it sounds exactly like something I'd want and I get very excited
> DA> but when I think about it carefully, it seems otherwise.
>
> 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.
Yes, I understand all that... I know what it is as a library component.
What I don't see is how *at the user level* it can easily and usefully
be exploited.
>>> Then the registry should be able to tell you what group it came from,
>>> too, I think?
>
> DA> Maybe... I'm still not sure how to use it. But I'll take another look.
>
> Simply call it like this (for message-ID "34"):
>
> (gnus-registry-get-id-key "34" 'group)
> (gnus-registry-get-id-key "34" 'subject)
"34" sounds like a message number, not a Message-ID (like what's found
in mail headers). How is gnus-registry going to know which group's
number 34 I'm referencing?
> gnus-registry.el has most of the install info at the beginning if you
> want to try it out.
I re-installed it yesterday, thanks.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-09-27 15:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:24 Dave Abrahams
2011-09-16 15:05 ` gnus-warp-to-article (was: nnir, gnus-goto-article and such) Dave Abrahams
2011-09-21 18:03 ` nnir, gnus-goto-article and such Lars Magne Ingebrigtsen
2011-09-21 21:16 ` John Wiegley
2011-09-22 13:01 ` Andrew Cohen
2011-09-26 19:17 ` Lars Magne Ingebrigtsen
2011-09-26 20:46 ` Dave Abrahams
2011-09-27 7:04 ` John Wiegley
2011-09-27 15:36 ` Dave Abrahams
2011-09-26 20:01 ` Dave Abrahams
2011-09-26 21:35 ` Ted Zlatanov
2011-09-27 15:35 ` Dave Abrahams [this message]
2011-09-27 21:12 ` Ted Zlatanov
2011-09-28 14:34 ` Dave Abrahams
2011-09-29 0:32 ` Ted Zlatanov
2011-09-29 1:19 ` Dave Abrahams
2011-09-29 2:06 ` Dave Abrahams
2011-09-29 8:27 ` Ted Zlatanov
2011-09-29 13:40 ` Dave Abrahams
2011-09-29 14:00 ` Ted Zlatanov
2011-09-29 14:40 ` Dave Abrahams
2011-09-29 14:58 ` Ted Zlatanov
2011-09-29 20:04 ` Dave Abrahams
2011-09-29 23:40 ` Ted Zlatanov
2011-09-29 8:22 ` Ted Zlatanov
2011-09-27 16:04 ` Dave Abrahams
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=m2wrcu0zht.fsf@pluto.luannocracy.com \
--to=dave@boostpro.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).