unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 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: Sat, 17 Nov 2018 16:36:40 +0200	[thread overview]
Message-ID: <83k1lbu5xj.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBdLoibvn4MPHndr5hoZ_oZOPPecDpei71s2PvegGkeCVA@mail.gmail.com> (message from Pip Cet on Sat, 17 Nov 2018 14:14:04 +0000)

> From: Pip Cet <pipcet@gmail.com>
> Date: Sat, 17 Nov 2018 14:14:04 +0000
> Cc: 33414@debbugs.gnu.org
> 
> > > (let ((inhibit-changing-match-data t)) (backtrace))
> > >
> > > into the *scratch* buffer and evaluate with C-M-x.)
> >
> > This works on the release branch, so I think it's a regression that
> > needs to be fixed.
> 
> If I'm testing correctly,
> 
> (let ((inhibit-changing-match-data t)) (debug))
> 
> fails on both branches

You are right, not sure what I did wrong when trying it a few moments
ago.





  reply	other threads:[~2018-11-17 14:36 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 [this message]
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
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=83k1lbu5xj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33414@debbugs.gnu.org \
    --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).