From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 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 15:50:52 +0000 [thread overview]
Message-ID: <20190430155052.GE4142@ACM> (raw)
In-Reply-To: <83d0l3sdzg.fsf@gnu.org>
Hello, Eli.
On Tue, Apr 30, 2019 at 18:35:15 +0300, Eli Zaretskii wrote:
> > From: "Basil L. Contovounesios" <contovob@tcd.ie>
> > Cc: Eli Zaretskii <eliz@gnu.org>, <28850@debbugs.gnu.org>
> > Date: Tue, 30 Apr 2019 14:44:27 +0100
> > > I'm just thinking, maybe this fix should have gone into the emacs-26
> > > branch. Not sure about that.
> > The patch looks unproblematic enough to me, but that is, of course,
> > Eli's call.
> Btw, I'm not sure I understand the need for calling (point) in that
> patch. Both functions return the value of point, and they both return
> LIMIT if they fail to find a match, so just testing the return value
> against LIMIT should be enough, no?
What happens is the search-forward-regexp finds a match entirely before
LIMIT, but the body of the loop processes the entire construct
introduced by that match and leaves point at the end of the construct.
This can be after LIMIT. Hence the check on (point) before the
search-forward-regexp.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-04-30 15:50 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
2019-04-30 13:44 ` Basil L. Contovounesios
2019-04-30 15:35 ` Eli Zaretskii
2019-04-30 15:50 ` Alan Mackenzie [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190430155052.GE4142@ACM \
--to=acm@muc.de \
--cc=28850@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
/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.