From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80096 Path: news.gmane.org!not-for-mail From: Dave Abrahams Newsgroups: gmane.emacs.gnus.general Subject: Re: nnir, gnus-goto-article and such Date: Wed, 28 Sep 2011 22:06:37 -0400 Message-ID: References: <87pqinvvg4.fsf@lifelogs.com> <87aa9pu1tx.fsf@lifelogs.com> <878vp8nq6y.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: dough.gmane.org 1317262902 18287 80.91.229.12 (29 Sep 2011 02:21:42 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 02:21:42 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28390@lists.math.uh.edu Thu Sep 29 04:21:38 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 1R96Fm-0000gl-3q for ding-account@gmane.org; Thu, 29 Sep 2011 04:21:38 +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 1R96FI-0003nW-Ru; Wed, 28 Sep 2011 21:21:08 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1R96FH-0003nM-L7 for ding@lists.math.uh.edu; Wed, 28 Sep 2011 21:21:07 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R96FF-0004wr-AP for ding@lists.math.uh.edu; Wed, 28 Sep 2011 21:21:07 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R96FC-0005Us-GF for ding@gnus.org; Thu, 29 Sep 2011 04:21:02 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R96F8-0000Tt-Vq for ding@gnus.org; Thu, 29 Sep 2011 04:20:58 +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 ; Thu, 29 Sep 2011 04:20:58 +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 ; Thu, 29 Sep 2011 04:20:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 67 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:xmvx2CFV2YAYmRENk0tSp1aIItU= X-Spam-Score: -5.4 (-----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80096 Archived-At: --=-=-= Content-Type: text/plain on Wed Sep 28 2011, Dave Abrahams wrote: > What I'd want to do with the registry is get gnus-summary-refer-article > to put in the registry the group in which it finds the article, so > gnus-warp-to-article will go to *that* group when I try to get to the > whole thread. > >> to = destination group, your group > > I don't think I want gnus to remember that the article is in my group. > I want it to be like an nnir group, where Gnus remembers the group in > which the article was originally found. So, thanks, you seem to have gotten me over one hump... here's my patch: --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=gnus-sum.patch Modified lisp/gnus-sum.el diff --git a/lisp/gnus-sum.el b/lisp/gnus-sum.el index 423de35..8452bb9 100644 --- a/lisp/gnus-sum.el +++ b/lisp/gnus-sum.el @@ -9077,6 +9077,13 @@ non-numeric or nil fetch the number specified by the (setq number (gnus-summary-insert-subject message-id))) ;; and display the article. (gnus-summary-select-article nil nil nil number) + (when (bound-and-true-p gnus-registry-install) + (let ((header (gnus-summary-article-header (gnus-summary-article-number)))) + (gnus-registry-handle-action + message-id nil + (gnus-method-to-full-server-name gnus-override-method) + (mail-header-subject header) + (mail-header-from header)))) (throw 'found t))) (gnus-message 3 "Couldn't fetch article %s" message-id))))))) --=-=-= Content-Type: text/plain But now, of course, gnus-warp-to-article doesn't consult the registry to find out the article's group, so `A T' still fails. For some reason, it goes directly to the backend, only one of which supports warping: nnir. [Aside: it seems like this territory is full of components that could in principle be nicely generalized, but whose implementation has only been made to work for one specific usage scenario] would it work if nnregistry supported warping? I don't really understand where/how that backend comes into play. > Note: nnir doesn't use the registry, but has its *own* record of which > group was the source of each article. Why? Dunno. -- Dave Abrahams BoostPro Computing http://www.boostpro.com --=-=-=--