From 50bfbe5fc0d39f79634f36cefd313a92d5fca7e0 Mon Sep 17 00:00:00 2001 From: Stefan Monnier Date: Wed, 26 Apr 2006 05:33:11 +0000 Subject: [PATCH] Minor tweaks. --- lispref/modes.texi | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/lispref/modes.texi b/lispref/modes.texi index 12e419e8e37..3f56179231c 100644 --- a/lispref/modes.texi +++ b/lispref/modes.texi @@ -3079,8 +3079,8 @@ While this works well most of the time, sometimes it doesn't---for example, when a buffer change has changed the syntactic meaning of text on an earlier line. -You can enlarge (or even reduce) the region to fontify by setting either -of the following variables: +You can enlarge (or even reduce) the region to fontify by setting @c either of +the following variables: @defvar font-lock-extend-region-function This buffer-local variable is either @code{nil} or is a function that @@ -3091,10 +3091,9 @@ The function is given three parameters, the standard @var{beg}, @var{end}, and @var{old-len} from after-change-functions (@pxref{Change Hooks}). It should return either a cons of the beginning and end buffer positions (in that order) of the region to fontify, or @code{nil} (which -directs the caller to fontify the default region). This function need -not preserve point or the match-data, but must preserve the current -restriction. The region it returns may start or end in the middle of a -line. +directs the caller to fontify the default region). This function needs +to preserve point, the match-data, and the current restriction. +The region it returns may start or end in the middle of a line. Since this function is called after every buffer change, it should be reasonably fast. -- 2.39.5