From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Cleaning up bogus newsgroups from newsrc.eld
Date: 19 Dec 2000 21:59:57 -0500 [thread overview]
Message-ID: <2nu27z23wy.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <76hf4hlihz.fsf@newjersey.ppllc.com>
Jake Colman <colman@ppllc.com> writes:
> >>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>
> ZSH> Jake Colman <colman@ppllc.com> writes:
> >> How can I trim cruft from my newsrc.eld? The number of newsgroups are
> >> getting larger and larger yet I know many of them are bogus. Is there
> >> a way to trim the size of that file? It iakes FOREVER to execute an
> >> A-k command!
>
> ZSH> (setq gnus-save-killed-list nil)
>
> If I set this to nil, the killed newsgroups will not be saved in my
> newsrc.eld file. Fine. And since I've already set
> `gnus-check-new-newsgroups' to `ask-server', I'll still get an
> accurate listing of all new newsgroups as they get carried by my
> news server. Also fine. But if I do this how do I then see a list
> of all available newsgroups if I decide I want to subscribe to
> something to which I am not currently subscribed? Currently, I may
> not have an interest in any comp.x.* newsgroups. What if something
> chages I want to see what comp.x.* newsgroups are available? Since
> I routinely kill all my zombies, won't these killed groups
> disappear? And, if so, how can I then see what groups are carried
> by my server?
You could browse the server to find out new groups.
Now, I've changed the behavior of `C-k', that is, if a group is killed
twice, it will no longer be in gnus-killed-list.
ShengHuo
next prev parent reply other threads:[~2000-12-20 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 2:02 Jake Colman
2000-12-06 2:10 ` ShengHuo ZHU
2000-12-06 14:41 ` Jake Colman
2000-12-07 18:51 ` Paul Jarc
2000-12-20 2:59 ` ShengHuo ZHU [this message]
2000-12-20 3:40 ` Cleaning up bogus completion buffers [was newsgroups] Harry Putnam
2000-12-20 5:36 ` ShengHuo ZHU
2000-12-20 9:17 ` Harry Putnam
2000-12-20 14:14 ` ShengHuo ZHU
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=2nu27z23wy.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).