unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64459@debbugs.gnu.org
Subject: bug#64459: 30.0.50; Edebug can't instrument certain syntax-propertize-rules forms
Date: Tue, 04 Jul 2023 19:02:02 +0300	[thread overview]
Message-ID: <838rbvll6t.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRsp2zv7cLu4RvDO+35r8vH1Vz=jQ4GoBDTWD3fZ1fovQ@mail.gmail.com> (message from Philipp Stephani on Tue, 4 Jul 2023 16:06:01 +0200)

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Tue, 4 Jul 2023 16:06:01 +0200
> Cc: 64459@debbugs.gnu.org
> 
> Am Di., 4. Juli 2023 um 15:42 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
> >
> > > From: Philipp Stephani <p.stephani2@gmail.com>
> > > Date: Tue, 04 Jul 2023 15:35:01 +0200
> > >
> > > This fails on master and emacs-29, but not on emacs-28, so it's a
> > > regression that I think should be fixed before releasing Emacs 29.
> >
> > The part about this not being a problem in Emacs 28 is not true: if I
> > try this in Emacs 28.2, I see in *Messages*:
> >
> >   Edebug: foo
> >   Eager macro-expansion failure: (void-function edebug-after)
> 
> Ah, indeed. So it looks like the actual change between 28 and 29 is
> that macroexpansion failures are now hard errors.
> The easiest way to fix this is to replace the first `form' in the
> edebug spec with `sexp'.

Adding Stefan.





  reply	other threads:[~2023-07-04 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 13:35 bug#64459: 30.0.50; Edebug can't instrument certain syntax-propertize-rules forms Philipp Stephani
2023-07-04 13:42 ` Eli Zaretskii
2023-07-04 14:06   ` Philipp Stephani
2023-07-04 16:02     ` Eli Zaretskii [this message]
2023-07-04 20:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 23:45   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05  9:34     ` Philipp Stephani
2023-07-05 11:33       ` Eli Zaretskii
2023-07-05 12:43         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 13:35           ` Eli Zaretskii
2023-07-05 15:37             ` 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=838rbvll6t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64459@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=p.stephani2@gmail.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.
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).