Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: .newsrc.eld is a black hole for old groups
Date: Mon, 21 Sep 2009 07:09:01 -0400	[thread overview]
Message-ID: <84d45kh7w2.fsf@incoming.verizon.net> (raw)
In-Reply-To: <yb063bcr3td.fsf@osl2u223.oslo2.fast.no> (Steinar Bang's message	of "Mon, 21 Sep 2009 12:26:54 +0200")

>>>>> Tassilo Horn <tassilo@member.fsf.org>:
>> Steinar Bang <sb@dod.no> writes:

> Sorry.  I meant `C-k', which is bound to gnus-topic-kill-group which has
> the documentation
>  gnus-topic-kill-group is an interactive compiled Lisp function in `gnus-topic'.
>  (gnus-topic-kill-group &optional N DISCARD)

>  Kill the next N groups.

> I _think_ I verified at one point in time that this command cleared the
> group out of .newsrc.eld.  But... I'm not staking my life on it...

Yes, but you also need to have gnus-save-killed-list to nil, which I
think is not the default.  This keeps killed groups out of your
.newsrc.eld, but comes with a cost, as noted in the documentation:

  *If non-nil, save the list of killed groups to the startup file.
  If you set this variable to nil, you'll save both time (when starting
  and quitting) and space (both memory and disk), but it will also mean
  that Gnus has no record of which groups are new and which are old, so
  the automatic new newsgroups subscription methods become meaningless.

  You should always set `gnus-check-new-newsgroups' to `ask-server' or
  nil if you set this variable to nil.

  This variable can also be a regexp.  In that case, all groups that do
  not match this regexp will be removed before saving the list.

-- 
Dave Goldberg
david.goldberg6@verizon.net



  reply	other threads:[~2009-09-21 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 18:29 jidanni
2009-09-15 20:09 ` Tassilo Horn
2009-09-16  0:23   ` jidanni
2009-09-16  7:58     ` Tassilo Horn
2009-09-16  8:47       ` Vegard Vesterheim
2009-09-18 15:09         ` Steinar Bang
2009-09-18 18:18           ` Tassilo Horn
2009-09-21 10:26             ` Steinar Bang
2009-09-21 11:09               ` Dave Goldberg [this message]
2009-09-21 13:32                 ` Steinar Bang

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=84d45kh7w2.fsf@incoming.verizon.net \
    --to=david.goldberg6@verizon.net \
    --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).