From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Emacs 24...
Date: Tue, 21 Feb 2012 15:50:06 -0500 [thread overview]
Message-ID: <87ipizap35.fsf@lifelogs.com> (raw)
In-Reply-To: <m2obss3xyn.fsf@nwalsh.com>
On Tue, 21 Feb 2012 12:20:16 -0500 Norman Walsh <ndw@nwalsh.com> wrote:
NW> Andreas Schwab <schwab@linux-m68k.org> writes:
>> Norman Walsh <ndw@nwalsh.com> writes:
>>
>>> Debugger entered--Lisp error: (void-function eieio--defgeneric-init-form)
>>
>> Make sure you don't have any old version of eieio.el somewhere in your
>> load-path.
NW> Fair enough. I did think I'd checked that, but I'll check more
NW> carefully next time I have a chance to try it.
It's frustrating, how many times this has come up.
Ted
next prev parent reply other threads:[~2012-02-21 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 13:53 Norman Walsh
2012-02-21 15:36 ` Andreas Schwab
2012-02-21 17:20 ` Norman Walsh
2012-02-21 20:50 ` Ted Zlatanov [this message]
2012-02-22 12:21 ` ~/.gnus.registry.eioio (was Re: Emacs 24...) Norman Walsh
2012-02-22 12:56 ` Norman Walsh
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=87ipizap35.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).