From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80099 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 03:22:56 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87wrcrn4f3.fsf@lifelogs.com> References: <87pqinvvg4.fsf@lifelogs.com> <87aa9pu1tx.fsf@lifelogs.com> <878vp8nq6y.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 1317284633 11291 80.91.229.12 (29 Sep 2011 08:23:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 08:23:53 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28393@lists.math.uh.edu Thu Sep 29 10:23:49 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 1R9BuG-00025V-KP for ding-account@gmane.org; Thu, 29 Sep 2011 10:23:49 +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 1R9Btw-0005Mf-OJ; Thu, 29 Sep 2011 03:23:28 -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 1R9Btu-0005MR-0V for ding@lists.math.uh.edu; Thu, 29 Sep 2011 03:23:26 -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 1R9Btp-0007sj-5u for ding@lists.math.uh.edu; Thu, 29 Sep 2011 03:23:25 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R9Btn-0006Gs-DO for ding@gnus.org; Thu, 29 Sep 2011 10:23:19 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9Btl-0001tt-Oa for ding@gnus.org; Thu, 29 Sep 2011 10:23:17 +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 10:23:17 +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 10:23:17 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 81 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:P8RynV4eXWJjLjkzqVCnwm2gemU= X-Spam-Score: -4.2 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80099 Archived-At: On Wed, 28 Sep 2011 21:19:38 -0400 Dave Abrahams wrote: DA> on Wed Sep 28 2011, Ted Zlatanov wrote: >>>> or by subject, or by sender? >> DA> You can't split by subject or sender without the registry?! You're DA> kidding, right? Like I said, I never ask Gnus to shuffle mail into DA> different folders for me but that seems pretty basic. >> >> No, I mean it will split to the same group as other articles with the >> same subject or sender. So if I put your mails in "dave" it will figure >> out it should keep putting new ones in there. DA> ...which always seemed wrong to me. Some subject lines (e.g. "FYI") are DA> so common that it's not a good guide to threading. Since the message DA> has References: and In-Reply-To: headers, why not use those? We do, that's what splitting by parent does. But many clients don't do it properly. In my experience subject lines don't recur that often but yeah that's one possible way to misfile a message. Splitting by sender and recipient is less prone to such homonymous accidents. DA> What's a user going to *do* with registry marks? That's another tool DA> whose real utility escapes me. >> >> It lets the user define any marks they want, without reconfiguring Gnus >> and without storing them in the newsrc.eld, by message-ID and not >> article number. DA> IIRC, IMAP lets you do that anyway? But anyway, again, why would I want DA> to define new marks? I guess I can think of a use-case, but marks that DA> don't follow me to other mail clients are pretty limited. Most backends, especially NNTP, don't let you define marks at all. The whole point of custom marks is that we (the Gnus developers) haven't thought of them yet. The example ones are To-Do, Later, Work, and Personal. I add Perl and a few work-related tags that would make no sense for anyone else. >>>> (defun gnus-registry-handle-action (id from to subject sender >>>> &optional recipients) >> DA> Umm, sorry. That function isn't documented. How do I use it? How DA> would I get the group that gnus-summary-refer-article finds the message DA> in into the registry? I don't even see a parameter for group. >> >> id = message ID, a string >> from = source group, nil in your case for a new article DA> nil is not useful to me; the whole point of this exercise is to record DA> the group associated with an article. start with article groups = (A C) in each case below; from = nil, to = B: article created/noticed in group B => (A B C) from = A, to = B: article move from A to B => (B C) from = A, to = nil: article registry deletion from group A => (C) DA> What I'd want to do with the registry is get gnus-summary-refer-article DA> to put in the registry the group in which it finds the article, so DA> gnus-warp-to-article will go to *that* group when I try to get to the DA> whole thread. DA> I don't think I want gnus to remember that the article is in my group. DA> I want it to be like an nnir group, where Gnus remembers the group in DA> which the article was originally found. from = nil, to = noticed_group DA> Note: nnir doesn't use the registry, but has its *own* record of which DA> group was the source of each article. Why? Dunno. The registry is an optional package so nnir doesn't require it. The nnregistry backend tracks articles through the registry. Ted