From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: p.stephani2@gmail.com, pipcet@gmail.com, 33414@debbugs.gnu.org
Subject: bug#33414: 27.0.50; inhibit-changing-match-data can be t in syntax-propertize functions, breaking backtrace and looking-at
Date: Sun, 05 Sep 2021 12:55:00 +0300 [thread overview]
Message-ID: <83r1e3tki3.fsf@gnu.org> (raw)
In-Reply-To: <87v93fmk35.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 05 Sep 2021 11:45:50 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: p.stephani2@gmail.com, pipcet@gmail.com, 33414@debbugs.gnu.org
> Date: Sun, 05 Sep 2021 11:45:50 +0200
>
> >> +(make-obsolete-variable 'inhibit-changing-match-data nil "28.1")
> >
> > Really? why obsolete it?
>
> Because it's not used (and shouldn't be used). `save-match-data' is the
> proper way to achieve this in normal code.
It's a variable we had since Emacs 23. The proposed replacements are
only useful if your Lisp program actually calls the APIs you propose
to extend, but it won't do if you call higher-level APIs.
We can recommend not to use the variable where the extended APIs could
be used instead with the new optional argument, but I don't think we
should obsolete it, let alone remove it in the future.
next prev parent reply other threads:[~2021-09-05 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 13:30 bug#33414: 27.0.50; inhibit-changing-match-data can be t in syntax-propertize functions, breaking backtrace and looking-at Pip Cet
2018-11-17 13:46 ` Eli Zaretskii
2018-11-17 14:14 ` Pip Cet
2018-11-17 14:36 ` Eli Zaretskii
2021-08-12 13:11 ` Lars Ingebrigtsen
2021-09-04 18:39 ` Philipp
2021-09-04 19:33 ` bug#33414: [External] : " Drew Adams
2021-09-05 9:29 ` Lars Ingebrigtsen
2021-09-05 9:40 ` Eli Zaretskii
2021-09-05 9:45 ` Lars Ingebrigtsen
2021-09-05 9:55 ` Eli Zaretskii [this message]
2021-10-07 18:49 ` Lars Ingebrigtsen
2021-10-07 19:07 ` bug#33414: [External] : " Drew Adams
2021-10-07 19:11 ` Lars Ingebrigtsen
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=83r1e3tki3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33414@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--cc=pipcet@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).