--- 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 ---