From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Registry warning?
Date: Tue, 27 Sep 2011 16:49:04 -0500 [thread overview]
Message-ID: <87oby5slkf.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxek10p4.fsf@randomsample.de>
On Sun, 04 Sep 2011 23:01:43 +0200 David Engster <deng@randomsample.de> wrote:
DE> Dave Goldberg writes:
>> ~/.gnus/registry.eioio seems to be persistent - that is the file
>> doesn't get removed when I exit so I don't understand what might be
>> wrong with it when it wants to reload.
DE> The persistence of the registry depends on (featurep
DE> 'hashtable-print-readable), which is available on FSF Emacs >=23.2. Gnus
DE> should probably say something more meaningful on older Emacsen...
I thought EIEIO had its own persistence mechanism, not using
`hashtable-print-readable'? That was one of the reasons I switched to
it, so serialization would Just Work.
Ted
next prev parent reply other threads:[~2011-09-27 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 20:24 Dave Goldberg
2011-09-04 21:01 ` David Engster
2011-09-04 21:07 ` Dave Goldberg
2011-09-27 21:49 ` Ted Zlatanov [this message]
2011-09-28 7:29 ` David Engster
2011-09-29 0:21 ` Ted Zlatanov
2011-09-29 6:02 ` David Engster
2011-09-29 8:30 ` Ted Zlatanov
2011-09-29 17:52 ` David Engster
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=87oby5slkf.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).