unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 1297@emacsbugs.donarmstrong.com
Subject: bug#1297: font-lock-keywords-case-fold-search doc and usage
Date: Sun, 2 Nov 2008 20:44:01 -0800 (PST)	[thread overview]
Message-ID: <200811030444.mA34i1oB000823@mothra.ics.uci.edu> (raw)
In-Reply-To: <87od0xh600.fsf@cyd.mit.edu> (Chong Yidong's message of "Sun, 02 Nov 2008 21:56:31 -0500")

Chong Yidong <cyd@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)






  parent reply	other threads:[~2008-11-03  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87od0xh600.fsf@cyd.mit.edu>
2008-11-02 15:56 ` bug#1297: font-lock-keywords-case-fold-search doc and usage Dan Nicolaescu
2008-11-03  3:05   ` bug#1297: marked as done (font-lock-keywords-case-fold-search doc and usage) Emacs bug Tracking System
2008-11-03  4:44 ` Dan Nicolaescu [this message]
2008-11-03 15:19   ` bug#1297: font-lock-keywords-case-fold-search doc and usage Chong Yidong
2008-11-04  7:22     ` Dan Nicolaescu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811030444.mA34i1oB000823@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=1297@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).