From: David Engster <deng@randomsample.de>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: ding@gnus.org, cedet-devel@lists.sourceforg.net
Subject: Re: [CEDET-devel] Bug in gnus with cedet component eioio
Date: Sat, 01 Dec 2012 15:48:23 +0100 [thread overview]
Message-ID: <87txs5rfpk.fsf@randomsample.de> (raw)
In-Reply-To: <50BA110E.2040701@siege-engine.com> (Eric M. Ludlam's message of "Sat, 01 Dec 2012 09:15:42 -0500")
Eric M. Ludlam writes:
> I suspect you need a (require 'eieio) somewhere. Several autoload
> cookies were removed as CEDET was integrated into Emacs which could be
> causing the problem. The GNUS package probably should have that, but
> in the short term, you could put it in your registry.
No, I don't think that is the problem. More likely, the OP will have to
recompile Gnus with the new EIEIO he's using, because some macros have
changed.
-David
next prev parent reply other threads:[~2012-12-01 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 0:41 Easior
2012-12-01 14:15 ` [CEDET-devel] " Eric M. Ludlam
2012-12-01 14:48 ` David Engster [this message]
2012-12-06 3:02 ` Easior Lars
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=87txs5rfpk.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=cedet-devel@lists.sourceforg.net \
--cc=ding@gnus.org \
--cc=eric@siege-engine.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).