unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 28850@debbugs.gnu.org
Subject: bug#28850: 26.0.90; Error running timer 'jit-lock-stealth-fontify': (error "Invalid search bound (wrong side of point)")
Date: Tue, 30 Apr 2019 13:32:03 +0000	[thread overview]
Message-ID: <20190430133203.GC4142@ACM> (raw)
In-Reply-To: <8736lzirbn.fsf@tcd.ie>

Hello Basil.

On Tue, Apr 30, 2019 at 13:57:16 +0100, Basil L. Contovounesios wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > The cause of this is a (search-forward-regexp <regexp> limit t) in a loop, where
> > the code fails to check (< (point) limit) at the start.  In textprop.c in
> > master, it so happens that the last successful iteration of the loop
> > leaves point beyond limit.  So we get the exception.

> > This is easy to correct, but first I'm going to check for all the other
> > places where the same mistake occurs.  Expect a patch soon!

> How exciting!  Thanks for looking into this so quickly.

I've just committed a patch to all the usual places (including the
savannah master) which I'm confident will have fixed the bug.  Feel free
to test this (and tell me what isn't quite fixed ;-).

I'm just thinking, maybe this fix should have gone into the emacs-26
branch.  Not sure about that.

> -- 
> Basil

-- 
Alan Mackenzie (Nuremberg, Geramny).





  reply	other threads:[~2019-04-30 13:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-15 16:07 bug#28850: 26.0.90; Error running timer 'jit-lock-stealth-fontify': (error "Invalid search bound (wrong side of point)") Eli Zaretskii
2017-10-17 16:42 ` Alan Mackenzie
2017-10-22 20:13 ` Alan Mackenzie
2017-10-24 14:46   ` Eli Zaretskii
2017-10-24 20:33     ` Alan Mackenzie
2017-10-25 19:11       ` Alan Mackenzie
2017-10-26 16:44         ` Eli Zaretskii
2017-10-26 18:36           ` Alan Mackenzie
2019-04-30  1:51           ` Basil L. Contovounesios
2019-04-30  9:24             ` Alan Mackenzie
2019-04-30 11:33             ` Alan Mackenzie
2019-04-30 12:57               ` Basil L. Contovounesios
2019-04-30 13:32                 ` Alan Mackenzie [this message]
2019-04-30 13:44                   ` Basil L. Contovounesios
2019-04-30 15:35                     ` Eli Zaretskii
2019-04-30 15:50                       ` Alan Mackenzie
2019-05-06 18:44                     ` Alan Mackenzie
2019-05-07  0:35                       ` Basil L. Contovounesios
2019-04-30 15:30                   ` Eli Zaretskii
2019-04-30 15:43                     ` Alan Mackenzie
2019-04-30 15:26                 ` Eli Zaretskii
2019-05-01 18:49                   ` Eli Zaretskii
2019-05-04 12:41                     ` Alan Mackenzie
2019-05-04 13:36                       ` Eli Zaretskii
2019-05-05  9:06                         ` Alan Mackenzie
2019-05-06 15:35                           ` Eli Zaretskii
2019-05-06 18:10                             ` Alan Mackenzie

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=20190430133203.GC4142@ACM \
    --to=acm@muc.de \
    --cc=28850@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).