From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61459 Path: news.gmane.org!not-for-mail From: "Kevin Greiner" Newsgroups: gmane.emacs.gnus.general Subject: Re: Agent and gnus-group-clear-data Date: Sun, 4 Dec 2005 09:28:18 -0600 Message-ID: <200512040928.AA3014710@mail.ev1.net> Reply-To: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1133710871 9755 80.91.229.2 (4 Dec 2005 15:41:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 4 Dec 2005 15:41:11 +0000 (UTC) Original-X-From: ding-owner+m9990@lists.math.uh.edu Sun Dec 04 16:41:08 2005 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Eivyh-0001EK-Bb for ding-account@gmane.org; Sun, 04 Dec 2005 16:40:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1EivyU-0002DD-00; Sun, 04 Dec 2005 09:40:26 -0600 Original-Received: from nas01.math.uh.edu ([129.7.128.39]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1Eivos-0002D8-00 for ding@lists.math.uh.edu; Sun, 04 Dec 2005 09:30:30 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas01.math.uh.edu with esmtp (Exim 4.52) id 1Eivon-0001WI-8l for ding@lists.math.uh.edu; Sun, 04 Dec 2005 09:30:30 -0600 Original-Received: from webmail7.ev1.net ([207.218.192.62] helo=mail.ev1.net) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Eivom-0005Rm-00 for ; Sun, 04 Dec 2005 16:30:24 +0100 X-Sender: Original-To: , Reiner Steib X-Mailer: X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61459 Archived-At: No. I can see where people might want to clear marks (i.e. gnus- group-clear-data) without purging the content that they have downloaded. In this particular case, the old article numbers have been invalidated so Rahed needed to do both. There's a section in the manual on 'Changing Servers' that mentions gnus-group-clear-data. It needs to be updated to also reference gnus-agent-flush-cache (to purge the old articles). Do you think we should add another section named 'Renumbering Articles' to discuss the sort of problem that Rahed encountered? Kevin ---------- Original Message ---------------------------------- From: Reiner Steib Reply-To: Reiner Steib Date: Tue, 29 Nov 2005 13:48:27 +0100 >Hi, > >shouldn't `gnus-group-clear-data' also clear the agent data? > >See the following thread on gnu.emacs.gnus: > >| From: rahed >| Subject: article reset on the server >| Newsgroups: gnu.emacs.gnus >| Date: Fri, 25 Nov 2005 14:55:42 +0100 >| Message-ID: >| http://www.google.de/groups? as_umsgid=v9u0e01n7m.fsf@marauder.physik.uni-ulm.de&hl=en > >On Tue, Nov 29 2005, rahed wrote: > >> Reiner Steib writes: >>>> M-c cleared all article marks but article numbers are untouched. So >>>> after entering the group I can see only old subject names articles. New >>>> ones which do exist on the server are consequently seen as read by the gnus. >>> >>> `M-c' doesn't fail for me: >>> >>> ,----[ Output of `G E' before `M-c' ] >>> | ("gmane.announce" 3 >>> | ((1 . 7483) >>> | (7485 . 7492)) >>> | ((seen >>> | (7448 . 7492)))) >>> `---- >>> >>> Note that the read article ranges "(1 . 7483) (7485 . 7492)" disappear >>> after `M-c': >>> >>> ,----[ Output of `G E' after `M-c' ] >>> | ("gmane.announce" 3 nil nil) >>> `---- >>> >>> I noticed that `M c' doesn't clear the data in the .agentview file of >>> the group. Maybe this matters. >>> >>> ,----[ cat News/agent/nntp/localhost/gmane/announce/.agentview ] >>> | ((7448 . 732279) (7449 . 732279) [...] >>> | (7491 . 732279) (7492 . 732279)) >>> `---- >[...] >> Thank you for following me. After deleting .agentview for the group >> everything is back to normal. > >Bye, Reiner. >-- > ,,, > (o o) >---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ > > > ________________________________________________________________ Sent via the EV1 webmail system at mail.ev1.net