From: Simon Josefsson <jas@extundo.com>
Subject: Re: auto-compressing nnml articles and overview files
Date: Wed, 05 Nov 2003 21:58:21 +0100 [thread overview]
Message-ID: <iluptg6ilci.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4n1xsmj0vz.fsf@koz.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 05 Nov 2003 10:22:40 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Also, I have some large overview files in ~/News/overview,
> e.g. "nnimap.mail.lifelogs.com.ding.1047497850.novcache".
> Considering I don't use the Agent, do I need those overview files?
> They seem to be caching the gnus-newsgroup-data. Can I remove them
> and regenerate them later, either automatically or manually?
It is safe to remove, if you agentize your nnimap servers.
** ~/News/overview/ not used.
As a result of the following change, the ~/News/overview/ directory is
not used any more. You can safely delete the entire hierarchy.
** gnus-agent
The Gnus Agent has seen a major update. It is now enabled by default,
and all nntp and nnimap servers from `gnus-select-method' and
`gnus-secondary-select-method' are agentized by default. Earlier only
the server in `gnus-select-method' was agentized by the default, and the
agent was disabled by default. When the agent is enabled, headers are
now also retrieved from the Agent cache instead of the backends when
possible. Earlier this only happened in the unplugged state. You can
enroll or remove servers with `J a' and `J r' in the server buffer.
Gnus will not download articles into the Agent cache, unless you
instruct it to do so, though, by using `J u' or `J s' from the Group
buffer. You revert to the old behaviour of having the Agent disabled
by customizing `gnus-agent'. Note that putting `(gnus-agentize)' in
~/.gnus is not needed any more.
prev parent reply other threads:[~2003-11-05 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 15:22 Ted Zlatanov
2003-11-05 15:51 ` Jesper Harder
2003-11-05 17:09 ` Kevin Greiner
2003-11-05 20:58 ` Simon Josefsson [this message]
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=iluptg6ilci.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).