From: Alan Mackenzie <acm@muc.de>
To: help-gnu-emacs@gnu.org
Subject: Re: c++-mode: Invalid function: (setq ad-return-value?(ad-Orig-c-parse-state))
Date: Wed, 27 Mar 2013 11:07:09 +0000 (UTC) [thread overview]
Message-ID: <kiujst$2vd1$1@colin.muc.de> (raw)
In-Reply-To: mailman.22894.1364329129.855.help-gnu-emacs@gnu.org
Hi, Andrew.
Andrew Pennebaker <andrew.pennebaker@gmail.com> wrote:
> [-- text/plain, encoding 7bit, charset: ISO-8859-1, 34 lines --]
> Updated<https://github.com/mcandre/mcandre/tree/4b8512cf84c4e3553d43182a8a5c72f6f37566f8/cpp/fizzy>code
> example. I had to copy and paste `i` and `{` on lines 48 and 49,
> because Emacs kept complaining
> "Invalid function: (setq ad-return-value (ad-Orig-c-parse-state))"
> On Tue, Mar 26, 2013 at 4:12 PM, Andrew Pennebaker <
> andrew.pennebaker@gmail.com> wrote:
>> I can't insert important C++ characters into my code (attached). When I
>> press ; or { Emacs shows an error in the minibuffer:
>> "Invalid function: (setq ad-return-value (ad-Orig-c-parse-state))"
>> Major mode is c++-mode.
>> Using Emacs 24.2.1.
>> --
>> Cheers,
>> Andrew Pennebaker
>> www.yellosoft.us
Like Leo suggested, it looks like somebody's put a `defadvice' on
c-parse-state, though I've no idea why that should produce an "Invalid
function" error. The code for advice has changed somewhat between Emacs
24.2 and 24.3.
Can you say why c-parse-state was advised? Possibly for debugging? In
that context, I would strongly advise you upgrade your Emacs to 24.3. In
Emacs 24.2, c-parse-state was buggy, and now it is, well, less buggy. ;-)
> --
> Cheers,
> Andrew Pennebaker
> www.yellosoft.us
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2013-03-27 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 20:12 c++-mode: Invalid function: (setq ad-return-value (ad-Orig-c-parse-state)) Andrew Pennebaker
2013-03-26 20:18 ` Andrew Pennebaker
2013-03-27 6:43 ` Leo Liu
2013-03-27 12:16 ` Andrew Pennebaker
[not found] ` <mailman.22894.1364329129.855.help-gnu-emacs@gnu.org>
2013-03-27 11:07 ` Alan Mackenzie [this message]
2013-03-27 12:37 ` Stefan Monnier
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='kiujst$2vd1$1@colin.muc.de' \
--to=acm@muc.de \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).