From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 74666@debbugs.gnu.org, ideasman42@gmail.com
Subject: bug#74666: 31.0.50; Regression in replace-match with empty-adjacent groups
Date: Sat, 28 Dec 2024 13:38:14 +0200 [thread overview]
Message-ID: <8634i8t4ux.fsf@gnu.org> (raw)
In-Reply-To: <jwvzfkvknwt.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)
> Cc: 74666@debbugs.gnu.org
> Date: Mon, 16 Dec 2024 22:18:57 -0500
> From: Stefan Monnier via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> > In this case, the match data is set with `set-match-data' using
> > calculated ranges.
>
> I guess we can take this as good thing: it means complexifying the
> regexp code would be wasted. 🙂
>
> > Since this used to work I think it's reasonable to consider it a regression.
>
> I was not trying to say it's not a regression. Just pouting because the
> old behavior was just a lucky accident and recovering it without losing
> the other improvement isn't completely straightforward.
>
> > I've since committed a workaround to evil-numbers [1], although I'd suspect
> > this would impact others.
>
> [ And the workaround relies on another lucky accident: the "easiest"
> fix for the problem would break your workaround. 🙁 ]
What should we do with this bug report?
next prev parent reply other threads:[~2024-12-28 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 10:56 bug#74666: 31.0.50; Regression in replace-match with empty-adjacent groups Campbell Barton
2024-12-03 14:05 ` Eli Zaretskii
2024-12-14 9:43 ` Eli Zaretskii
2024-12-14 16:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 1:10 ` Campbell Barton
2024-12-17 3:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-28 11:38 ` Eli Zaretskii [this message]
2024-12-28 15:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-28 16:33 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8634i8t4ux.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74666@debbugs.gnu.org \
--cc=ideasman42@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.