GNU bug report logs - #16307
24.3.50; doc string of `font-lock-keywords' - typo

Previous Next

Full log

View this message in rfc822 format

From: Matthew Leach <matthew <at> mattleach.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16307 <at> debbugs.gnu.org
Subject: bug#16307: 24.3.50; doc string of `font-lock-keywords' - typo
Date: Tue, 14 Jan 2014 20:30:52 +0000

[Message part 1 (text/plain, inline)]

Hello

Drew Adams <drew.adams <at> oracle.com> writes:

> "it is produced internal by..." should presumably be "it is produced
> internally by..."

[...]

Here is a small patch to fix this up.

lisp/Changelog

2014-01-14  Matthew Leach  <matthew <at> mattleach.net>

	* font-lock.el (font-lock-keywords): Fix typo in variable
	documentation (bug#16307).

[font-lock-keywords-doc-fix.patch (text/x-patch, inline)]

diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 27829ff..7e9131d 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -458,7 +458,7 @@ This variable is set by major modes via the variable `font-lock-defaults'.
 Be careful when composing regexps for this list; a poorly written pattern can
 dramatically slow things down!
 
-A compiled keywords list starts with t.  It is produced internal
+A compiled keywords list starts with t.  It is produced internally
 by `font-lock-compile-keywords' from a user-level keywords list.
 Its second element is the user-level keywords list that was
 compiled.  The remaining elements have the same form as

[Message part 3 (text/plain, inline)]

-- 
Matt

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.