From: Matthew Leach <matthew@mattleach.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16307@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 [thread overview]
Message-ID: <m2vbxml30j.fsf@mattleach.net> (raw)
In-Reply-To: <698553df-cd63-49e4-a4c7-19349fac4b52@default> (Drew Adams's message of "Tue, 31 Dec 2013 09:11:55 -0800 (PST)")
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
Hello
Drew Adams <drew.adams@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@mattleach.net>
* font-lock.el (font-lock-keywords): Fix typo in variable
documentation (bug#16307).
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: font-lock-keywords-doc-fix.patch --]
[-- Type: text/x-patch, Size: 655 bytes --]
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
[-- Attachment #3: Type: text/plain, Size: 10 bytes --]
--
Matt
next prev parent reply other threads:[~2014-01-14 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 17:11 bug#16307: 24.3.50; doc string of `font-lock-keywords' - typo Drew Adams
2014-01-14 20:30 ` Matthew Leach [this message]
2014-01-14 20:38 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vbxml30j.fsf@mattleach.net \
--to=matthew@mattleach.net \
--cc=16307@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.