From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/50383 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: message registry for Gnus Date: Tue, 25 Feb 2003 12:57:59 -0500 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: owner-ding@hpc.uh.edu Message-ID: <4nbs105jko.fsf@chubby.bwh.harvard.edu> References: <4n3cn9i6kq.fsf@lockgroove.bwh.harvard.edu> <4nznopxxn5.fsf@lockgroove.bwh.harvard.edu> <4nbs11wv0q.fsf@chubby.bwh.harvard.edu> <4nr89xz5q2.fsf@chubby.bwh.harvard.edu> <84znok3jzm.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1046197131 7785 80.91.224.249 (25 Feb 2003 18:18:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 25 Feb 2003 18:18:51 +0000 (UTC) Return-path: Original-Received: from hermes.netfonds.no ([80.91.224.195]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18njcG-0001m5-03 for ; Tue, 25 Feb 2003 19:15:44 +0100 Original-Received: from malifon.math.uh.edu (malifon.math.uh.edu [129.7.128.13]) by hermes.netfonds.no (8.12.1/8.12.1) with ESMTP id h1PI1lFs016353 for ; Tue, 25 Feb 2003 19:01:47 +0100 (CET) Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 18njLX-0003H6-00; Tue, 25 Feb 2003 11:58:27 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 25 Feb 2003 11:59:25 -0600 (CST) Original-Received: from sclp3.sclp.com (sclp3.sclp.com [66.230.238.2]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id LAA09960 for ; Tue, 25 Feb 2003 11:59:08 -0600 (CST) Original-Received: (qmail 72882 invoked by alias); 25 Feb 2003 17:58:05 -0000 Original-Received: (qmail 72875 invoked from network); 25 Feb 2003 17:58:00 -0000 Original-Received: from clifford.bwh.harvard.edu (134.174.9.41) by 66.230.238.6 with SMTP; 25 Feb 2003 17:58:00 -0000 Original-Received: from chubby.bwh.harvard.edu (chubby [134.174.9.50]) by clifford.bwh.harvard.edu (8.10.2+Sun/8.11.0) with ESMTP id h1PHvxj19959 for ; Tue, 25 Feb 2003 12:57:59 -0500 (EST) Original-Received: (from tzz@localhost) by chubby.bwh.harvard.edu (8.11.6+Sun/8.11.0) id h1PHvxr11897; Tue, 25 Feb 2003 12:57:59 -0500 (EST) Original-To: ding@gnus.org 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-Followup-To: ding@gnus.org In-Reply-To: <84znok3jzm.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Tue, 25 Feb 2003 08:19:41 +0100") User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:50383 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:50383 On Tue, 25 Feb 2003, kai.grossjohann@uni-duisburg.de wrote: > Ted Zlatanov writes: > >> OK, so where can I insert a hook for the registry, if all I care >> for is the first time a message is seen in a group, with the >> article's header data available? I would prefer to avoid the >> braindead solution of scanning all articles in a newsgroup and >> noticing the new ones every time - although that might not be too >> hard if I look at the "unseen" articles. > > Do you want to see the article again after it has moved to another > group? It might not be unseen anymore at that point. I can track the article at that point with the move hook - it's only the first time I see it that I need to initialize its registry entry. In other words, an article's life is like this: spool -> group1 -> move -> group2 -> delete \-> copy -> group3 -> delete I can track everything except the "spool -> group1" part. The main reason why I want to register the article when it's in the Gnus newsgroup data, rather than when it's spooled by nnmail, is that at spool time the data in the article may be malformed. For instance, the message ID (which is crucial for tracking the message) may be invalid when nnmail spools the article (cf. discussion on article numbers yesterday on this list). There's a better chance that I'll get a "good" message ID if I grab it from the Gnus newsgroup data, rather than parsing it out of the spooled message. As far as the user is concerned, registering the article at spool time vs. registering it at the time of summary entry is the same thing. I think. Ted