From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: message registry for Gnus
Date: Wed, 16 Apr 2003 16:35:26 -0400 [thread overview]
Message-ID: <4n8yuayycx.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <4n3cn9i6kq.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 31 Jan 2003 12:15:33 -0500")
On Fri, 31 Jan 2003, tzz@lifelogs.com wrote:
> - track messages by ID
>
> - associate a Lisp structure (probably a list, hashes are too new?)
> with a message ID
This is working, in a first-draft-please-put-me-out-of-my-misery sort
of way. I store message headers separately from message spool data.
Please take a look and let me know what you think (gnus-registry.el
with the definitions of gnus-registry-alist and
gnus-registry-headers-alist in gnus.el). I'm pretty sure there's bugs
in the code.
> - store the registry in a separate file or in the newsrc.eld?
Right now, the registry is stored in the newsrc.eld. This may be a
problem later - it will grow quickly. We can either compress the
registry or move it to a separate file; removing old registry entries
would probably be OK for deleted messages but we have to be careful
with copies of a message (removal of a copy means we have to keep the
records for the original around). Ideas welcome.
Ted
prev parent reply other threads:[~2003-04-16 20:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 17:15 Ted Zlatanov
2003-02-01 10:28 ` Kai Großjohann
2003-02-01 16:39 ` Lars Magne Ingebrigtsen
2003-02-01 20:20 ` Ted Zlatanov
2003-02-02 12:10 ` Lars Magne Ingebrigtsen
2003-02-02 15:14 ` Ted Zlatanov
2003-02-07 12:20 ` Lars Magne Ingebrigtsen
2003-02-02 16:54 ` Kai Großjohann
2003-02-03 20:47 ` Ted Zlatanov
2003-02-04 15:25 ` Simon Josefsson
2003-02-04 19:57 ` Ted Zlatanov
2003-02-05 5:56 ` Simon Josefsson
2003-02-07 20:43 ` Ted Zlatanov
2003-02-02 0:35 ` Raja R Harinath
2003-02-02 1:30 ` Ted Zlatanov
2003-02-02 17:15 ` Raja R Harinath
2003-02-07 20:48 ` Ted Zlatanov
2003-02-07 21:10 ` Lars Magne Ingebrigtsen
2003-02-07 22:45 ` Ted Zlatanov
2003-02-08 20:39 ` Lars Magne Ingebrigtsen
2003-02-21 19:05 ` Ted Zlatanov
2003-02-22 22:20 ` Lars Magne Ingebrigtsen
2003-02-24 15:36 ` Ted Zlatanov
2003-02-24 16:58 ` Andreas Fuchs
2006-09-28 13:20 ` gnus-registry: alist-to-hashtable, hashtable-to-alist (was: message registry for Gnus) Reiner Steib
2006-09-28 14:21 ` gnus-registry: alist-to-hashtable, hashtable-to-alist Ted Zlatanov
2006-09-28 16:03 ` CHENG Gao
2006-09-28 16:58 ` Reiner Steib
2003-02-24 21:57 ` message registry for Gnus Lars Magne Ingebrigtsen
2003-02-24 22:14 ` Ted Zlatanov
2003-02-25 7:19 ` Kai Großjohann
2003-02-25 17:57 ` Ted Zlatanov
2003-03-28 9:20 ` Ted Zlatanov
2003-04-16 20:35 ` Ted Zlatanov [this message]
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=4n8yuayycx.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).