GNU bug report logs -
#1297
font-lock-keywords-case-fold-search doc and usage
Previous Next
Reported by: Dan Nicolaescu <dann <at> ics.uci.edu>
Date: Sun, 2 Nov 2008 16:05:05 UTC
Severity: normal
Done: Chong Yidong <cyd <at> stupidchicken.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Chong Yidong <cyd <at> stupidchicken.com> writes:
> > 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.
Thanks.
> > 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.
But that's not quite right, not sure about the standard, but there are
lisps that are case insensitive:
(DEFUN foo (arg)
blah)
ought to be fontified the same was as:
(defun foo (arg)
blah)
This bug report was last modified 16 years and 203 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.