bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1297: marked as done (font-lock-keywords-case-fold-search doc and us


From: Emacs bug Tracking System
Subject: bug#1297: marked as done (font-lock-keywords-case-fold-search doc and usage)
Date: Sun, 2 Nov 2008 19:05:06 -0800

Your message dated Sun, 02 Nov 2008 21:56:31 -0500
with message-id <87od0xh600.fsf@cyd.mit.edu>
and subject line Re: font-lock-keywords-case-fold-search doc and usage
has caused the Emacs bug report #1297,
regarding font-lock-keywords-case-fold-search doc and usage
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
1297: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1297
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems
--- Begin Message --- Subject: font-lock-keywords-case-fold-search doc and usage Date: Sun, 2 Nov 2008 07:56:33 -0800 (PST)
font-lock-keywords-case-fold-search docstring should make it more clear
that font-lock-defaults erases it.

There is one victim in the tree.  `lisp-mode' does:

  (make-local-variable 'font-lock-keywords-case-fold-search)
  (setq font-lock-keywords-case-fold-search t)

but the value of font-lock-keywords-case-fold-search in a lisp-mode
buffer is nil, that's because font-lock-defaults does a
kill-local-variable on it...





--- End Message ---
--- Begin Message --- Subject: Re: font-lock-keywords-case-fold-search doc and usage Date: Sun, 02 Nov 2008 21:56:31 -0500
> font-lock-keywords-case-fold-search docstring should make it more clear
> that font-lock-defaults erases it.

Okay, I changed it to make it hopefully clearer.

> There is one victim in the tree.  `lisp-mode' does:
>
>   (make-local-variable 'font-lock-keywords-case-fold-search)
>   (setq font-lock-keywords-case-fold-search t)
>
> but the value of font-lock-keywords-case-fold-search in a lisp-mode
> buffer is nil, that's because font-lock-defaults does a
> kill-local-variable on it...

Great catch.  No one has complained about this, so clearly it's OK for
font-lock-keywords-case-fold-search to be nil.  I removed the bogus
8-year-old setting of font-lock-keywords-case-fold-search.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]