From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Fix for gnus-registry on newer Emacsen
Date: Fri, 22 Feb 2013 22:07:24 +0100 [thread overview]
Message-ID: <87k3q083cj.fsf@randomsample.de> (raw)
Probably no one noticed, but if you use the registry on the current
pretest or trunk, you'll get a message on startup about an "Unsafe call
to eieio-persistent-read".
I'll just pushed a fix for this, but of course we have to stay
compatible with older Emacsen, so I had to wrap this in a condition-case
and an additional with-no-warnings. However, it seems the latter doesn't
have any effect on XEmacs, so the buildbot is red there. Does anyone
know what can be done here?
-David
next reply other threads:[~2013-02-22 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 21:07 David Engster [this message]
2013-02-22 21:36 ` Dave Abrahams
2013-02-24 13:49 ` David Engster
2013-02-24 21:02 ` Uwe Brauer
2013-02-24 21:14 ` 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=87k3q083cj.fsf@randomsample.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).