From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8666 Path: main.gmane.org!not-for-mail From: Wesley.Hardaker@sphys.unil.ch Newsgroups: gmane.emacs.gnus.general Subject: Discussion: To del cached articles upon zapping group info? Date: 08 Nov 1996 15:17:04 +0100 Organization: Universite de Lausanne, BSP Sender: whardake@iptsun2.unil.ch Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035148799 13553 80.91.224.250 (20 Oct 2002 21:19:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:19:59 +0000 (UTC) Return-Path: Original-Received: (qmail 7136 invoked from smtpd); 8 Nov 1996 14:44:14 -0000 Original-Received: from ifi.uio.no (0@129.240.64.2) by deanna.miranova.com with SMTP; 8 Nov 1996 14:44:13 -0000 Original-Received: from unilmta3.unil.ch (cisun29a.unil.ch [130.223.27.29]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Fri, 8 Nov 1996 15:18:52 +0100 Original-Received: from iptsun2.unil.ch by unilmta3.unil.ch with SMTP inbound; Fri, 8 Nov 1996 15:18:29 +0100 Original-Received: by iptsun2.unil.ch (5.x/Unil-3.1/) id AA07935; Fri, 8 Nov 1996 15:17:06 +0100 Original-To: ding@ifi.uio.no X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4 X-Url: http://www.ece.ucdavis.edu/~hardaker Original-Lines: 30 X-Mailer: Red Gnus v0.56/XEmacs 19.14 Xref: main.gmane.org gmane.emacs.gnus.general:8666 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8666 Lars and I have been going back and forth about the following situation: When I zapped my group attributes (ie, numbers associated with read articles) gnus didn't clear my cache, which affected what it thought was the current article range later on. For instance, I had an article cached in comp.protocols.snmp with a article number of 832 or something like that, but the articles in the newsgroup were now 1-315 or so (due to the new news server). Gnus keyt saying there were no new articles because it had marked 1-832 as read after the first time I read the group... We are trying to decide what it should do about the cached articles... In the above situation, its horrible (no new news till after 832 appears). I said it should delete the cached articles, simply because they are no longer valid and will conflict with new numbered articles. There is simply no place in the 1-* range for them as they have been taken up by new numbers. I suppose you could re-order them to something like -3 -> -1 or something similar, but I don't know how gnus would handle that (this is a new idea Lars). So, in the end, Lars needs other suggestions? Ideas? Wes