Gnus development mailing list
 help / color / mirror / Atom feed
From: jidanni@jidanni.org
To: ding@gnus.org
Subject: .newsrc.eld is a black hole for old groups
Date: Wed, 16 Sep 2009 02:29:51 +0800	[thread overview]
Message-ID: <87fxao9i3k.fsf@jidanni.org> (raw)

Gentlemen, check your .newsrc.eld files.
You will find tons of crap groups you thought you had totally deleted
long ago.
The funny thing is there is no
(info "(gnus) Listing Groups")
key that will list them, C-u argument or not.
You might think C-u A k might show them, but it shows a lot more too,
and whatever you do will not get them out of your .newsrc.eld file.

This I can see in *Group*
  ("nnrss:DebCentral" 6 (1)
   ((seen (1 . 19)))
   (nnrss "")
   ((timestamp 17376 17743)))

But this is in no way accessible there:
  ("gmane.comp.handhelds.openmoko.announce" 6
   ((1 . 62))
   ((seen (1 . 62)) (save 54)) nil
   ((timestamp 18814 473)))

So I conclude the .newsrc.eld file is a never ending black hole that can
fill up with old groups, with no interface available to the user to
clean it up ever, short of open heart surgery on the .newsrc.eld file itself.

Apparently once a group falls off the gnus-topic-alist, its records
become orphan data in the .newsrc.eld file... a "memory leak"?

Also in ~/News there are files corresponding to those newsgroups with no
other way to clean them up other than going in by hand...

Nothing special in http://jidanni.org/comp/configuration/ to cause it.



             reply	other threads:[~2009-09-15 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 18:29 jidanni [this message]
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
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=87fxao9i3k.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --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).