From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: Expiring in agent directories and .agentview files
Date: 15 Feb 1998 23:13:21 +0000 [thread overview]
Message-ID: <m3u3a0fomm.fsf@lotusland.demon.co.uk> (raw)
Hi,
I seem to remember Lars maybe saying that the `gnus-agent-expire'
function was not perhaps working as well as it should and hence it
wasn't documented.
This being the case, I was wondering how others using the agent to
read their news offline were expiring articles? I've been using
`gnus-agent-expire' and, with the exception of a few corrupted
.overview lines, it seems to do the job. However :-), although the
.overview lines are deleted along with their corresponding article
files in the news directories, I can't help but notice that my
.agentview files appear to carry on growing.
I currently deal with growing .history files with a cron job, but
.agentview files are presumably a little more important. Does anyone
know how things are supposed to be in respect of these files?
TIA
--
Mike.
next reply other threads:[~1998-02-15 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-15 23:13 Mike McEwan [this message]
1998-02-16 2:12 ` Lars Magne Ingebrigtsen
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=m3u3a0fomm.fsf@lotusland.demon.co.uk \
--to=mike@lotusland.demon.co.uk \
/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).