summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2016-11-04 11:16:40 +0200
committerEli Zaretskii <eliz@gnu.org>2016-11-04 11:16:40 +0200
commitbdc89eb4a6fa977f050551b43a299999aa3dda57 (patch)
tree537ef9e29cdf6fc59f8afae6222c6a2ae68826d6
parent4a0c590cbf4db96fb62877dd662c6bdeef7aeab1 (diff)
downloademacs-bdc89eb4a6fa977f050551b43a299999aa3dda57.tar.gz
Improve documentation of 'font-lock-remove-keywords'
* doc/lispref/modes.texi (Customizing Keywords): Clarify the 'keywords' argument of 'font-lock-remove-keywords'. Suggested by Hong Xu <hong@topbug.net>. (Bug#24830)
-rw-r--r--doc/lispref/modes.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi
index 32baa27147b..7bbb5e6f583 100644
--- a/doc/lispref/modes.texi
+++ b/doc/lispref/modes.texi
@@ -2916,7 +2916,9 @@ This function removes @var{keywords} from @code{font-lock-keywords}
for the current buffer or for major mode @var{mode}. As in
@code{font-lock-add-keywords}, @var{mode} should be a major mode
command name or @code{nil}. All the caveats and requirements for
-@code{font-lock-add-keywords} apply here too.
+@code{font-lock-add-keywords} apply here too. The argument
+@var{keywords} must exactly match the one used by the corresponding
+@code{font-lock-add-keywords}.
@end defun
For example, the following code adds two fontification patterns for C