Subject: bug#24830: closed (Re: bug#24830: [PATCH] Add an example for font-lock-remove-keywords.)

From: [email-masked] (GNU bug Tracking System)
Date: Fri, 04 Nov 2016 09:21:01 +0000

Your bug report

#24830: [PATCH] Add an example for font-lock-remove-keywords.

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
24830: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24830
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#24830: [PATCH] Add an example for font-lock-remove-keywords.
From: Eli Zaretskii <[email-masked]>
To: Hong Xu <[email-masked]>
Cc: [email-masked]
Date: Fri, 04 Nov 2016 11:20:49 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

> From: Hong Xu <[email-masked]>
> Date: Sun, 30 Oct 2016 16:24:47 -0700
> 
>  doc/lispref/ChangeLog.1 |  4 ++++
>  doc/lispref/modes.texi  | 10 ++++++++++
>  2 files changed, 14 insertions(+)
> 
> diff --git a/doc/lispref/ChangeLog.1 b/doc/lispref/ChangeLog.1
> index 610e7541e7de..34c7b5634359 100644
> --- a/doc/lispref/ChangeLog.1
> +++ b/doc/lispref/ChangeLog.1
> @@ -1,3 +1,7 @@
> +2016-10-30  Hong Xu  <[email-masked]>
> +
> +	* modes.texi (Customizing Keywords): Add an example for `font-lock-remove-keywords'.
> +

Thanks.  I added the caveat to the documentation of
'font-lock-remove-keywords'.  I don't see a particular need to have an
example for its use, as just saying the argument 'keywords' should be
identical to what was used by 'font-lock-add-keywords' seems to be
enough.

With that, I'm closing the bug report.  Thanks.

Btw, you are encouraged to start the legal paperwork for assigning
copyright of your contributions to the FSF, so that we could accept
your contributions without any limitations.

Subject: [PATCH] Add an example for font-lock-remove-keywords.
From: Hong Xu <[email-masked]>
To: [email-masked]
Date: Sun, 30 Oct 2016 16:24:47 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

---
 doc/lispref/ChangeLog.1 |  4 ++++
 doc/lispref/modes.texi  | 10 ++++++++++
 2 files changed, 14 insertions(+)

diff --git a/doc/lispref/ChangeLog.1 b/doc/lispref/ChangeLog.1
index 610e7541e7de..34c7b5634359 100644
--- a/doc/lispref/ChangeLog.1
+++ b/doc/lispref/ChangeLog.1
@@ -1,3 +1,7 @@
+2016-10-30  Hong Xu  <[email-masked]>
+
+	* modes.texi (Customizing Keywords): Add an example for `font-lock-remove-keywords'.
+
 2015-03-29  Glenn Morris  <[email-masked]>
 
 	* objects.texi (Equality Predicates): Fix typo in example.
diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi
index 32baa27147bf..04d1f13c60d2 100644
--- a/doc/lispref/modes.texi
+++ b/doc/lispref/modes.texi
@@ -2930,6 +2930,16 @@ Customizing Keywords
    ("\\<\\(and\\|or\\|not\\)\\>" . font-lock-keyword-face)))
 @end smallexample
 
+To remove the fontification of the word @samp{FIXME} above, use the
+following code.  Note that the list in the argument @var{keywords}
+must be exactly the same as the one added by
+@code{font-lock-add-keywords}.
+
+@smallexample
+(font-lock-remove-keywords 'c-mode
+ '(("\\<\\(FIXME\\):" 1 font-lock-warning-face prepend)))
+@end smallexample
+
 @noindent
 This example affects only C mode proper.  To add the same patterns to C
 mode @emph{and} all modes derived from it, do this instead:
-- 
2.1.4