unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jens Schmidt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: monnier@iro.umontreal.ca, 66219@debbugs.gnu.org
Subject: bug#66219: 29.1.50; edebug + syntax-propertize-rules + rx => eager macro expansion failure
Date: Wed, 27 Sep 2023 22:01:49 +0200	[thread overview]
Message-ID: <87r0mj75ci.fsf@sappc2.fritz.box> (raw)
In-Reply-To: <877cocs1c0.fsf@web.de> (Michael Heerdegen's message of "Wed, 27 Sep 2023 06:10:39 +0200")

forcemerge 64459 66219
thanks

Michael Heerdegen <michael_heerdegen@web.de> writes:

> This looks like Bug#65620 which has been fixed recently.  I don't get an
> error for your recipe with master.

Actually, it more seems like bug#64459 fixed by Stefan in 26f31fe3b584.
Merging accordingly since it is not worth separately fixing in 29, IMO.





  reply	other threads:[~2023-09-27 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 20:43 bug#66219: 29.1.50; edebug + syntax-propertize-rules + rx => eager macro expansion failure Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-27  4:10 ` Michael Heerdegen
2023-09-27 20:01   ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-27 20:16     ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-28 19:46       ` Stefan Kangas
2023-09-28 20:02         ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-29 14:51           ` Eli Zaretskii
2023-09-27 20:23 ` bug#66219: 29.1.50; edebug + syntax-propertize-rules + rx =>, " Jens Schmidt 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=87r0mj75ci.fsf@sappc2.fritz.box \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66219@debbugs.gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=michael_heerdegen@web.de \
    --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).