From 3eb1d3a0f8a7cf1bd46d4fa411c2eb73b26bfab7 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Mon, 6 Oct 2014 20:20:33 -0700 Subject: [PATCH] * lisp/font-lock.el (font-lock-fontify-buffer): Fix interactive-only markup. --- lisp/ChangeLog | 4 ++++ lisp/font-lock.el | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 88096b3e78c..2d60bd5d630 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,7 @@ +2014-10-07 Glenn Morris + + * font-lock.el (font-lock-fontify-buffer): Fix interactive-only markup. + 2014-10-07 Wilson Snyder Sync with upstream verilog-mode revision c075a492. diff --git a/lisp/font-lock.el b/lisp/font-lock.el index 0a6a0e80d15..22444277ba2 100644 --- a/lisp/font-lock.el +++ b/lisp/font-lock.el @@ -1047,7 +1047,7 @@ The region it returns may start or end in the middle of a line.") ;; Of course, this function doesn't do all of the above in all situations ;; (e.g. depending on whether jit-lock is in use) and it can't guess what ;; the caller wants. - (interactive-only "use font-lock-ensure or font-lock-flush instead.")) + (interactive-only "use `font-lock-ensure' or `font-lock-flush' instead.")) (interactive "p") (font-lock-set-defaults) (let ((font-lock-verbose (or font-lock-verbose interactively))) -- 2.11.4.GIT