From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Invalid function error in cl.el
Date: Thu, 23 Feb 2006 10:57:44 -0500 [thread overview]
Message-ID: <87ek1u1336.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 87oe0zcb6b.fsf@cisco.com
> This clip is in buffer-stack.el
> (incf buffer-stack-index)
> I replaced it with
> (setq buffer-stack-index (1+ buffer-stack-index))
You don't need to replace it, it was perfectly valid. But maybe the file is
missing an (eval-when-compile (require 'cl)) at its top.
> Everything works as expected now, which is good, but this literally
> worked for 3 years. I have no idea why it would break now. Eh,
> anyway, thanks for the prod in the right direction.
You probably recompiled buffer-stack.el and this recompilation was done when
CL was not loaded, which resulted in a broken buffer-stack.elc.
Stefan
next prev parent reply other threads:[~2006-02-23 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 21:11 Invalid function error in cl.el John Russell
2006-02-22 21:36 ` Pascal Bourguignon
2006-02-22 21:53 ` John Russell
2006-02-23 15:57 ` Stefan Monnier [this message]
2006-02-24 0:35 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ek1u1336.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).