From: Paul Moore <gustav@morpheus.demon.co.uk>
Subject: Re: Cacheing the active file
Date: Wed, 8 May 2002 15:11:37 +0200 [thread overview]
Message-ID: <1ycmbx3f.fsf@morpheus.demon.co.uk> (raw)
In-Reply-To: <vafwuuf541h.fsf@lucy.cs.uni-dortmund.de>
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> Paul Moore <gustav@morpheus.demon.co.uk> writes:
>
> > This would seem to me to imply that the killed list is saved
> > somewhere, but the server is asked about new groups. Fair enough, but
> > I see no evidence of any of the groups on the server which I am *not*
> > subscribed to (which would presumably be killed groups) in any of the
> > files on my PC.
>
> If you hit C-k on a group, Gnus will store that group name in
> ~/.newsrc.eld under the killed list. Does this help?
Not really, unfortunately. Mainly because if I start gnus unplugged,
then do ^ to get to the groups buffer, and press RET on my NNTP server
to get the active list, I still get nothing, even if the killed groups
*are* in my ~/.newsrc.eld.
Also, because they only get stored if I subscribe and then do C-k, not
if I was never subscribed to them. This is clumsy, and it also means
there is no way of me requesting a list of the new groups from the
server.
I guess this isn't possible :-( Oh well, I have a (clumsy) workaround
in the form of manually saving the server's active file, and
refreshing it occasionally (via a full re-read). It just seems odd
that the agent doesn't cache the active file for offline use, and
offer a "get new groups" function to keep the cached list update. (Or
at least offer something functionally equivalent).
Paul.
prev parent reply other threads:[~2002-05-08 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <offs2jeg.fsf@morpheus.demon.co.uk>
2002-05-08 10:26 ` Kai Großjohann
2002-05-08 13:11 ` Paul Moore [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=1ycmbx3f.fsf@morpheus.demon.co.uk \
--to=gustav@morpheus.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).