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: Tue, 28 Apr 2009 22:45:37 +0200 [thread overview]
Message-ID: <87ljpkld72.fsf@freebits.de> (raw)
In-Reply-To: jwvy6tkwymx.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > what is the difference between the variables
> > `font-lock-extend-region-functions'
> > and
> > `font-lock-extend-after-change-region-function' ?
> > In particular, how do they relate? Which should be used for what?
>
> Have you read the Elisp manual's discussion about font-locking
> multiline elements?
No, I somehow missed that section. Of course, it's all in there! (blush)
> 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).
>
> > I face the following problem: Font-lock, perhaps just jit-lock (I'm
> > using that), calls `font-lock-fontify-region-function' with start and
> > end values pretty much arbitrary in the buffer.
>
> Yes, that's normal. That's what font-lock-extend-region-functions is for.
Right, works like a charm now.
Thank you very much for your prompt answer!,
-T.
next prev parent reply other threads:[~2009-04-28 20:45 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 [this message]
2009-04-29 10:42 ` Tobias C. Rittweiler
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=87ljpkld72.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).