From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: gnus-registry rewrite
Date: Tue, 05 Apr 2011 11:28:39 -0500 [thread overview]
Message-ID: <878vvo64so.fsf@lifelogs.com> (raw)
There is a new gnus-registry.el in the master branch. The paint is
barely dry. Here's what's new:
- fewer variables per square inch (many obsoleted)
- all the data management is in registry.el
- EIEIO-based and very fast to save/read the file; now it's in
~/.gnus.registry.eieio so you can use your old registry from an older
Gnus without a problem.
- secondary indices handle everything, including the group for an
article, for very fast lookups (no more list traversals)
- ERT tests: run "emacs -batch -L . -l ert.el -l gnus-registry.el -f ert-run-tests-batch-and-exit
What's missing: documentation. So try it out and see what works and
what doesn't; if there are no changes or outstanding bugs in a few days
I'll write the documentation.
Ted
next reply other threads:[~2011-04-05 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 16:28 Ted Zlatanov [this message]
2011-04-05 17:56 ` Ted Zlatanov
2011-04-06 8:10 ` Kan-Ru Chen
2011-04-06 10:53 ` Ted Zlatanov
2011-04-06 17:29 ` Kan-Ru Chen
2011-04-06 17:37 ` Ted Zlatanov
2011-04-17 13:22 Andrew Cohen
2011-04-18 18:17 ` Andrew Cohen
2011-04-20 20:41 ` Ted Zlatanov
2011-04-20 20:48 ` 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=878vvo64so.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).