From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 66979@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#66979: Wrong number of arguments with completion-at-point
Date: Tue, 07 Nov 2023 19:02:28 -0500 [thread overview]
Message-ID: <jwvmsvpaza9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ZUrDFN8mVFxebq7s@ACM> (Alan Mackenzie's message of "Tue, 7 Nov 2023 23:07:00 +0000")
> What has happened is that the advice macroexpand-advice in
> elisp--local-variables has been applied to macroexpand-1, and due to the
> typo there, never gets removed (now fixed with bug #65622). This piece
> of advice is what suppresses the backtrace.
Ah, right, so we're actually not inside `elisp--local-variables` any
more, it's just that the advice was left by error.
> But I think I added the debug to that condition-case handler before
> spotting and correcting the typo in macroexpand[-1]. So it may well be
> that that debug could be removed without great damage.
Exactly. Thanks,
Stefan
next prev parent reply other threads:[~2023-11-08 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 7:13 bug#66979: Wrong number of arguments with completion-at-point Juri Linkov
2023-11-07 17:53 ` Juri Linkov
2023-11-07 18:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-07 19:50 ` Alan Mackenzie
2023-11-07 20:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-07 23:07 ` Alan Mackenzie
2023-11-08 0:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-09 7:32 ` Juri Linkov
2023-11-12 21:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvmsvpaza9.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66979@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=juri@linkov.net \
--cc=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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).