From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Copley <rcopley@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 40661@debbugs.gnu.org
Subject: bug#40661: Crash in regex search during redisplay
Date: Wed, 30 Sep 2020 05:49:17 +0200 [thread overview]
Message-ID: <87a6x79b5u.fsf@gnus.org> (raw)
In-Reply-To: <CAPM58oh0s5Jm7Asz8d-wD0JnZAJpVtJj_JDwNh+etkGEvUjdkg@mail.gmail.com> (Richard Copley's message of "Tue, 21 Apr 2020 00:04:23 +0100")
Richard Copley <rcopley@gmail.com> writes:
>> And second, it freezes relocation at a
>> higher level than needed, above the re_match_2_internal function which
>> is the only one that can call Lisp.
>
> Right, but freeze_buffer_relocation was surely done like that on
> purpose, to hoist it outside the loop in search_buffer_re. Anyway, I'm
> sure it's no big deal.
If I'm skimming this thread correctly, the reported bug was fixed by Eli
at the time, and there was then some followup discussion. But there
doesn't seem to be anything more to be done here, so I'm closing this
bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-30 3:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 14:35 bug#40661: Crash in regex search during redisplay Richard Copley
2020-04-16 15:36 ` Eli Zaretskii
2020-04-16 16:33 ` Eli Zaretskii
2020-04-16 16:42 ` Daniel Colascione
2020-04-16 16:56 ` Richard Copley
2020-04-16 17:24 ` Daniel Colascione
2020-04-16 19:35 ` Richard Copley
2020-04-17 11:22 ` Eli Zaretskii
2020-04-17 13:55 ` Eli Zaretskii
2020-04-17 14:01 ` Daniel Colascione
2020-04-17 15:28 ` Stefan Monnier
2020-04-17 15:50 ` Eli Zaretskii
2020-04-17 16:00 ` Stefan Monnier
2020-04-18 11:57 ` Eli Zaretskii
2020-04-20 18:30 ` Richard Copley
2020-04-20 19:06 ` Eli Zaretskii
2020-04-20 23:04 ` Richard Copley
2020-09-30 3:49 ` Lars Ingebrigtsen [this message]
2020-04-16 16:57 ` 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
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=87a6x79b5u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40661@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rcopley@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).