From: "Tobias C. Rittweiler" <tcr@freebits.de>
To: emacs-devel@gnu.org
Subject: Re: `font-lock-extend-region-functions' vs. `font-lock-extend-after-change-region-function'
Date: Wed, 29 Apr 2009 12:42:56 +0200 [thread overview]
Message-ID: <873abr211r.fsf@freebits.de> (raw)
In-Reply-To: jwvy6tkwymx.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The "right" answer is usually font-lock-extend-region-functions, but
> it's hard to tell without knowing anything more (sometimes it's
> difficult/impossible to write the necessary
> font-lock-extend-region-functions).
Let EXTEND be a function that's pushed onto
`font-lock-extend-region-functions', and let MARKER be font-lock search
function that's specified in `font-lock-keywords'.
I get the following call chain:
extend: (1, 523) --> t (1, 701)
extend: (1, 701) --> nil (1, 701)
marker: pt=1 limit=701 ==> nil
extend: (523, 1034) --> t (483, 1156)
^^^
extend: (483, 1156) --> nil (483, 1156)
marker: pt=483 limit=1156
(The values in parentheses are font-lock-beg, and font-lock-end.)
As you see, EXTEND extends the region to be fontified from (1, 523) to
(1, 701). MARKER cannot find anything in that region.
But the new region that EXTEND is called with begins at 523, and not 701
even though we processed the region between 523 and 701 already.
This seems more inefficient than it needs to be if I'm not missing
anything.
-T.
PS: I'm using `jit-lock' as font-lock-support-mode.
next prev parent reply other threads:[~2009-04-29 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 15:34 `font-lock-extend-region-functions' vs. `font-lock-extend-after-change-region-function' Tobias C. Rittweiler
2009-04-28 16:10 ` Stefan Monnier
2009-04-28 20:45 ` Tobias C. Rittweiler
2009-04-29 10:42 ` Tobias C. Rittweiler [this message]
2009-04-29 13:46 ` Stefan Monnier
2009-04-29 17:40 ` Tobias C. Rittweiler
2009-04-29 20:26 ` Stefan Monnier
2009-04-29 20:45 ` Samuel Bronson
2009-04-29 20:53 ` Stefan Monnier
2009-05-01 16:37 ` Tobias C. Rittweiler
2009-05-04 19:08 ` Stefan Monnier
2009-05-07 12:30 ` Tobias C. Rittweiler
2009-05-16 12:26 ` Tobias C. Rittweiler
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=873abr211r.fsf@freebits.de \
--to=tcr@freebits.de \
--cc=emacs-devel@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 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).