Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Modification to newsrc saving, please check!
Date: Tue, 20 May 2003 13:37:39 -0400	[thread overview]
Message-ID: <4niss5ecyk.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <84bry0fwn6.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Sun, 18 May 2003 11:10:21 +0200")

On Sun, 18 May 2003, kai.grossjohann@gmx.net wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> It would be nice if the gnus-save-newsrc-file function was more
>> modular, so I could save the registry cache through it instead of
>> essentially copying it into gnus-registry-cache-save.  The idea of
>> saving variables to a file in a way that would let us just (load)
>> that file is very convenient.  We should facilitate it as much as
>> possible for other areas of Gnus.
> 
> Sounds like a plan.  So how about making it more modular?  Obvious
> parameters that I see is the way that the contents of the
> buffer/file are generated, and also filename and coding and
> suchlike.

I'll think about it, maybe an association table of symbols with file
names and nil means the regular place.

Specifically for the registry, however, I may have to change the
format yet again.  Saving the whole registry with every update is
pretty inefficient.  I'm thinking of your format for the nnmail cache,
with the extra data stored as a Lisp expression at the end of the
line.  Something like:

Message-ID group1 group2 group3 '((creation-time 10000000))

It's much faster to use this, but of course more work is needed to
work around the limitations of the format.  Argh.  If only Emacs had a
built-in file database.

Ted



  reply	other threads:[~2003-05-20 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 16:26 Registry is working (first cut) Ted Zlatanov
2003-05-03 22:51 ` Raymond Scholz
2003-05-04 11:01   ` Reiner Steib
2003-05-08 14:05     ` Ted Zlatanov
2003-05-08 16:25       ` Karl Pflästerer
2003-05-08 18:47         ` Modification to newsrc saving, please check! (was: Registry is working (first cut)) Ted Zlatanov
2003-05-09 16:35           ` Modification to newsrc saving, please check! Ted Zlatanov
2003-05-18  9:10           ` Kai Großjohann
2003-05-20 17:37             ` Ted Zlatanov [this message]
2003-05-22  7:05               ` Kai Großjohann
2003-05-08 13:58   ` Registry is working (first cut) Ted Zlatanov
2003-05-09 17:10     ` Ted Zlatanov
2003-05-11 14:01     ` Raymond Scholz
2003-05-11 14:08       ` Raymond Scholz
2003-05-11 18:02       ` Ted Zlatanov
2003-05-12 19:16         ` Ted Zlatanov
2003-05-18  9:11     ` Kai Großjohann

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=4niss5ecyk.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.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).