From: Malcolm Purvis <malcolmp@xemacs.org>
To: ding@gnus.org
Subject: Re: move article, agent does not expire ?
Date: Wed, 03 Oct 2007 08:45:10 +1000 [thread overview]
Message-ID: <m2ve9p3zm1.fsf@xemacs.org> (raw)
In-Reply-To: <878x6mgdug.fsf@petole.dyndns.org> (Nicolas KOWALSKI's message of "Tue, 02 Oct 2007 09:44:39 +0200")
>>>>> "Nicolas" == Nicolas KOWALSKI <niko@petole.dyndns.org> writes:
Nicolas> But when I move an article from a group to another, this expiry
Nicolas> does not happen, and so old data is kept into the agent.
I see a similar problem using imap where the agent doesn't notice that
articles have been moved by another MUA (in my case Gnus running on
another machine, and no, both Gnus are not running at the same time).
Removing ~/News/agent fixes the problem, but is there some way to get
the agent to check automatically, when plugged, that the articles in its
cache still exist?
Malcolm
--
Malcolm Purvis <malcolmp@xemacs.org>
next prev parent reply other threads:[~2007-10-02 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 7:44 Nicolas KOWALSKI
2007-10-02 11:55 ` Greg Troxel
2007-10-02 13:58 ` Nicolas KOWALSKI
2007-10-02 22:45 ` Malcolm Purvis [this message]
2007-10-03 18:48 ` Elias Oltmanns
2007-10-03 18:54 ` Greg Troxel
2007-10-06 8:17 ` Malcolm Purvis
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=m2ve9p3zm1.fsf@xemacs.org \
--to=malcolmp@xemacs.org \
--cc=ding@gnus.org \
/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).