From: "Kevin Greiner" <kevin.greiner@compsol.cc>
Subject: Re: Agent and gnus-group-clear-data
Date: Sun, 4 Dec 2005 09:28:18 -0600 [thread overview]
Message-ID: <200512040928.AA3014710@mail.ev1.net> (raw)
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 <reinersteib+gmane@imap.cc>
Reply-To: Reiner Steib <Reiner.Steib@gmx.de>
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 <rahed@e-last-minute.com>
>| Subject: article reset on the server
>| Newsgroups: gnu.emacs.gnus
>| Date: Fri, 25 Nov 2005 14:55:42 +0100
>| Message-ID: <uek54omqp.fsf@e-last-minute.com>
>| 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 <reinersteib+from-uce@imap.cc> 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
next reply other threads:[~2005-12-04 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 15:28 Kevin Greiner [this message]
2005-12-04 18:44 ` Reiner Steib
2007-03-24 20:51 ` Reiner Steib
-- strict thread matches above, loose matches on Subject: below --
2005-11-29 12:48 Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512040928.AA3014710@mail.ev1.net \
--to=kevin.greiner@compsol.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).