Gnus development mailing list
 help / color / mirror / Atom feed
From: posting-list@MailAndNews.com (Jari Aalto+mail.emacs)
Subject: Feature request: Keepng meta-data out of newsrc.eld
Date: Thu, 17 Jan 2002 19:47:04 +0200	[thread overview]
Message-ID: <8zaw27l3.fsf@blue.sea.net> (raw)


Would it be possible to take out 

-   Group-specific information
-   Topic layout information
-   other meta-data 

and store these separate file out of newsrc.eld? I had an unfortunate
event the other day when downloading 4-years of archived mail
and integrating them into one virtual group for searching.
I dind have lot's of virtual memory, but somehow Emacs couldn't
allocate - or allocated only form physhical heap memory - I don't
know.

The net effect was that during creating the M-g virtual group, I got
"memory exhausted" and trying to save at least some, gnus/emacs
trashed my newsrc.el.

It was kind of a prayer moment looking at completely empty newsrc.eld.


Now I'm in a process of recreating everyting and I'm more convinced
that the meta-data should now be in one big newsrc.eld. It could hold
only the article numbers and ranges and stuff. The mailing list
parameters (to-list et all,) could be easily restored from separate
files, because the group informations does not much chnage once you
get it the way you want.

Any chance of looking on this?

Another idea could be to implement a "dump" that would generate
metadata out of the newsrc.el and a "re-dump" to restore the
metadata in event of failure. This could be a kind of 
backup system

I gather that, it doesn't make sense to backup newsrc.eld, because
it stores the article numbers, which keep changing, but the metadata 
could be backuppped easily, because it doensät change much if none
at all in the end.

Any comments?
Jari




             reply	other threads:[~2002-01-17 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 17:47 Jari Aalto+mail.emacs [this message]
2002-01-18 17:29 ` Simon Josefsson

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=8zaw27l3.fsf@blue.sea.net \
    --to=posting-list@mailandnews.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).