From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80119 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: nnir, gnus-goto-article and such Date: Thu, 29 Sep 2011 09:00:41 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87oby3jvna.fsf@lifelogs.com> References: <87pqinvvg4.fsf@lifelogs.com> <87aa9pu1tx.fsf@lifelogs.com> <878vp8nq6y.fsf@lifelogs.com> <87sjnfn486.fsf@lifelogs.com> Reply-To: ding@gnus.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317304879 24292 80.91.229.12 (29 Sep 2011 14:01:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 14:01:19 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28413@lists.math.uh.edu Thu Sep 29 16:01:15 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 1R9HAp-0005nX-Kb for ding-account@gmane.org; Thu, 29 Sep 2011 16:01:15 +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 1R9HAk-0007YB-BS; Thu, 29 Sep 2011 09:01:10 -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 1R9HAj-0007Xz-4O for ding@lists.math.uh.edu; Thu, 29 Sep 2011 09:01:09 -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 1R9HAe-0007Et-Qz for ding@lists.math.uh.edu; Thu, 29 Sep 2011 09:01:09 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R9HAd-0006Mx-F2 for ding@gnus.org; Thu, 29 Sep 2011 16:01:03 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9HAY-0005at-Sp for ding@gnus.org; Thu, 29 Sep 2011 16:00:58 +0200 Original-Received: from 38.98.147.133 ([38.98.147.133]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 16:00:58 +0200 Original-Received: from tzz by 38.98.147.133 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 16:00:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 63 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.133 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) Cancel-Lock: sha1:esOuySwETLx5CzvBHPxWN5lWV6U= X-Spam-Score: -4.2 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80119 Archived-At: On Thu, 29 Sep 2011 09:40:54 -0400 Dave Abrahams wrote: DA> in nnregistry.el there are no comments. There are a few: #+begin_src lisp ;; This file provides the `nnregistry' Gnus back-end. It can be used ;; in `gnus-refer-article-method' to quickly search for a message by ;; id, regardless of the back-end that stores it. See the Gnus manual ;; for usage examples and more information. #+end_src but yeah, it's a pretty new package. DA> in gnus-registry.el it says DA> ;; You should also consider using the nnregistry backend to look up DA> ;; articles. See the Gnus manual for more information. DA> The Gnus manual says almost nothing useful about nnregistry. It shows DA> how it can be used in gnus-refer-article-method, and I have done that. DA> What further enabling do you have in mind? That was it. >> 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. DA> IIUC from reading elsewhere you rewrote the registry. I wrote *registry.el but I was talking about nnir.el, nnregistry.el, and other search functionality. The registry is not a search engine so I thought you didn't mean it. I'm not sure how it could be generalized and in what direction--tell me what you think. >> At least for the registry I know it's optional so we can't depend on >> it. DA> I'm not sure what "optional" means in this context. Is Gnus going to DA> ship without the registry code? Users should be able to use every aspect of Gnus without calling `gnus-registru-initialize'. The memory usage of the gnus-registry, if we enabled it by default, would be unpleasant for many of our users on older or less capable machines. Thus any general Gnus functionality should not depend on the gnus-registry's availability. Furthermore the gnus-registry should be treated as a lossy cache. If you find something useful, great. But don't rely on it. That attitude lets us expire it more aggressively. There are "precious" properties you can set, so for instance the registry marks are not lost, but from our side we can't expect that. Ted