From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8077 Path: main.gmane.org!not-for-mail From: Scott Blachowicz Newsgroups: gmane.emacs.gnus.general Subject: Re: Message buffers associated with files? Date: Fri, 27 Sep 1996 08:45:59 -0700 Message-ID: References: <199609172045.PAA24878@mordor.rsn.hp.com> Reply-To: scott@statsci.com NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain X-Trace: main.gmane.org 1035148297 10010 80.91.224.250 (20 Oct 2002 21:11:37 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:11:37 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.6/8.6.9) with SMTP id JAA04854 for ; Fri, 27 Sep 1996 09:09:14 -0700 Original-Received: from nwnexus.wa.com (nwnexus.wa.com [192.135.191.1]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Fri, 27 Sep 1996 17:46:04 +0200 Original-Received: from main.statsci.com by nwnexus.wa.com with SMTP id AA24633 (5.65c/IDA-1.4.4 for ); Fri, 27 Sep 1996 08:46:00 -0700 Original-Received: from statsci.com [206.63.206.4] with smtp by main.statsci.com with smtp (/\oo/\ Smail3.1.29.1 #29.3 #3) id m0v6f72-0003wsC; Fri, 27 Sep 96 08:46 PDT X-Mailer: exmh version 1.6.9 8/22/96 Original-To: ding@ifi.uio.no In-Reply-To: Your message of "Fri, 27 Sep 1996 07:23:25 +0200." <199609270523.HAA25994@sunsite.auc.dk> Xref: main.gmane.org gmane.emacs.gnus.general:8077 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8077 > The issues with nngnats are even more difficult--files change, and you > want to notice when they do. Not only can the content change, but the > status can change as well--essentially, the back end wants to keep > track of some of the flags. And some files you want to see again > whenever they change, while others you don't want to see again. This > could be done through scoring, but the ideal thing would be to > redefine dormancy as articles which magically become either unread or > ticked when they change. (This works well with gnats, since you > should never have followups; you just keep adding to the same > document.) Another [probably full of holes] approach could be to have things like file update time used to synthesize a "message-id" for the files. That way, if the file changes, its message-id changes and it becomes a "new message" as far as a news reader is concerned. Maybe there could be some smarts in there to consider all revisions of the same file as part of the same thread? Hmmm...I suppose that also means an automatic "cancel" on the previous "message-id" too. Just some thought/brick-bat fodder... Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div) 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org