Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: message registry for Gnus
Date: Mon, 24 Feb 2003 10:36:21 -0500	[thread overview]
Message-ID: <4nbs11wv0q.fsf@chubby.bwh.harvard.edu> (raw)
In-Reply-To: <m38yw8ez3w.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 22 Feb 2003 23:20:51 +0100")

On Sat, 22 Feb 2003, larsi@gnus.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> Is the data header for the article available somehow at the point
>> of cache insertion in nnmail.el?
> 
> No, the header data is being built by Gnus upon group entry.  When
> nnmail is snarfing mail, it has no such structure.

Hrm.  Can I put the spool hook at a later point, just after the header
data is available?

>> Also, to save a hashtable, it seems like I have to convert it to an
>> alist and put that in a file, and convert the other way when I want
>> to load from a file.  Is there an easier way?
> 
> No, that's the way to do it.  :-)  Hash tables (well, obarrays,
> really) don't (to use a Javaish term) serialize very well.

Could something like hashtable-to-alist-string and
hashtable-from-alist-string be added to the Gnus core?  It would make
my life easier, and I'm definitely not the person to write reliable
versions of these functions :)  I think these functions could probably
be useful in other places as well; I looked but found no such
functionality already in place.

Serialization would be a wonderful feature for Emacs Lisp in general.

Thanks!
Ted



  reply	other threads:[~2003-02-24 15:36 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 [this message]
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

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=4nbs11wv0q.fsf@chubby.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).