summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorChong Yidong <cyd@stupidchicken.com>2007-04-23 14:39:40 +0000
committerChong Yidong <cyd@stupidchicken.com>2007-04-23 14:39:40 +0000
commitd439bcd8058181dec7b43115e1a99d1a897f8cf5 (patch)
treecb5dcea01871aa4b1be56ae67010ce59cac7fd1c /man
parent6ef234e266441b736dcd6456ad99372ce60834a8 (diff)
downloademacs-d439bcd8058181dec7b43115e1a99d1a897f8cf5.tar.gz
(Highlight Interactively): Correct description of hi-lock-file-patterns-policy.
Diffstat (limited to 'man')
-rw-r--r--man/display.texi14
1 files changed, 9 insertions, 5 deletions
diff --git a/man/display.texi b/man/display.texi
index 81ea723ddb8..6cb2d857165 100644
--- a/man/display.texi
+++ b/man/display.texi
@@ -726,12 +726,16 @@ match), and finally use this command (@code{hi-lock-find-patterns}) to
have Hi Lock highlight the edited patterns.
@vindex hi-lock-file-patterns-policy
-The variable @code{hi-lock-file-patterns-policy} controls whether
-@code{hi-lock-find-patterns} should really do anything. Its value can
-be @code{nil} (do nothing), @code{t} (extract the patterns),
-@code{ask} (query the user), or a function. If it is a function,
+The variable @code{hi-lock-file-patterns-policy} controls whether Hi
+Lock mode should automatically extract and highlight patterns found in
+a file when it is visited. Its value can be @code{nil} (never
+highlight), @code{t} (highlight the patterns), @code{ask} (query the
+user), or a function. If it is a function,
@code{hi-lock-find-patterns} calls it with the patterns as argument;
-if the function returns non-@code{nil}, the patterns are used.
+if the function returns non-@code{nil}, the patterns are used. The
+default is @code{nil}. Note that patterns are always highlighted if
+you call @code{hi-lock-find-patterns} directly, regardless of the
+value of this variable.
@vindex hi-lock-exclude-modes
Also, @code{hi-lock-find-patterns} does nothing if the current major