From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80067 Path: news.gmane.org!not-for-mail From: Dave Abrahams Newsgroups: gmane.emacs.gnus.general Subject: Re: nnir, gnus-goto-article and such Date: Tue, 27 Sep 2011 11:35:42 -0400 Message-ID: References: <87pqinvvg4.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317138100 10086 80.91.229.12 (27 Sep 2011 15:41:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 27 Sep 2011 15:41:40 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28361@lists.math.uh.edu Tue Sep 27 17:41:35 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R8Zmm-0008Jz-LC for ding-account@gmane.org; Tue, 27 Sep 2011 17:41:33 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1R8ZlV-0002Un-Kj; Tue, 27 Sep 2011 10:40:13 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1R8ZlT-0002Uc-Ts for ding@lists.math.uh.edu; Tue, 27 Sep 2011 10:40:11 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R8ZlP-0007Td-Uk for ding@lists.math.uh.edu; Tue, 27 Sep 2011 10:40:09 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R8ZlN-0002mS-VI for ding@gnus.org; Tue, 27 Sep 2011 17:40:05 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R8ZlN-0007WY-3v for ding@gnus.org; Tue, 27 Sep 2011 17:40:05 +0200 Original-Received: from 207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com ([207.172.223.249]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Sep 2011 17:40:05 +0200 Original-Received: from dave by 207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Sep 2011 17:40:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 59 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 207-172-223-249.c3-0.smr-ubr3.sbo-smr.ma.static.cable.rcn.com User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (darwin) Cancel-Lock: sha1:CEXR2A1TzwBGKNjHBs6jsFUIOVs= X-Spam-Score: -5.4 (-----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80067 Archived-At: on Mon Sep 26 2011, Ted Zlatanov wrote: > On Mon, 26 Sep 2011 16:01:52 -0400 Dave Abrahams wrote: > > DA> on Wed Sep 21 2011, Lars Magne Ingebrigtsen wrote: > >>> Dave Abrahams 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