From: Ted Zlatanov <tzz@lifelogs.com>
Subject: gnus-registry.el changes
Date: Thu, 04 Sep 2003 18:22:05 -0400 [thread overview]
Message-ID: <4n65k819f6.fsf@lockgroove.bwh.harvard.edu> (raw)
- tracking by subject: say you get messages with the same subject but
no references header (yes it's true, some MUAs don't generate those!
the horror!) - the registry will track them by subject. There is
some minimal tuning with gnus-registry-minimum-subject-length and I
simplify the subject. I had to modify quite a few backends to pass
a subject to nnmail-cache-insert. Let's see how well it works. My
tests were encouraging.
- caching extra data: for extra data like the subject or mtime, it's
all in an alist, and it's slow to traverse that repeatedly. So I
cache it dynamically in a hashtable inside the registry. The
secondary hashtable does not get saved with the registry.
The changes were pretty major so if gnus-registry.el barfs please
let me know... I tested the basics.
Thanks
Ted
next reply other threads:[~2003-09-04 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 22:22 Ted Zlatanov [this message]
2003-09-05 1:17 ` Danny Siu
2003-09-05 12:10 ` Ted Zlatanov
2003-09-05 12:34 ` Katsumi Yamaoka
2003-09-05 13:12 ` Ted Zlatanov
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=4n65k819f6.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).