From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: ERT tests on Emacs22
Date: Wed, 18 May 2011 17:38:40 +0200 [thread overview]
Message-ID: <m2pqnghvcv.fsf@ibookg4-c2.pc.gwdg.de> (raw)
In-Reply-To: <87mxik3vty.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 18 May 2011 09:52:09 -0500")
Ted Zlatanov writes:
> On Mon, 16 May 2011 15:16:15 +0200 David Engster <deng@randomsample.de> wrote:
> DE> trying to get the ERT tests to work on Emacs22, it occured to me that
> DE> you're depending on the hashtable-print-readable feature, which is only
> DE> available since Emacs 23.2? So I'm afraid you'll either have to restrict
> DE> the registry to newer Emacsen, or you'll have to create an object-write
> DE> method for registry-db which properly serializes hash-tables for older
> DE> Emacsen...
>
> Ugh. Well, the gnus-registry is an optional package so we could
> simply say it's not for older Emacsen and skip the ERT tests there.
> The package could, when loaded, complain if the feature is not
> available.
>
> I'd really like to avoid writing a hashtable serializer for the sake
> of Emacs 23.1 and older users. It's been missing since the
> gnus-registry.el rewrite and no one has complained, so I doubt it's a
> big population of people who want the latest Gnus yet can't upgrade
> their Emacs.
Perfectly fine with me; I'll drop the registry tests for Emacs22
then. BTW, XEmacs doesn't have the native serializer either; but as you
said, no one's complained yet...
-David
next prev parent reply other threads:[~2011-05-18 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2sjsedbvk.fsf@engster.org>
2011-05-18 14:52 ` Ted Zlatanov
2011-05-18 15:38 ` David Engster [this message]
2011-05-18 20:46 ` Ted Zlatanov
2011-05-19 6:51 ` David Engster
2011-05-19 10:11 ` Ted Zlatanov
2011-05-19 6:25 ` Gnus registry and Emacs <= 23.1 (was: ERT tests on Emacs22) Reiner Steib
2011-05-19 10:08 ` Gnus registry and Emacs <= 23.1 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=m2pqnghvcv.fsf@ibookg4-c2.pc.gwdg.de \
--to=deng@randomsample.de \
--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).