unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Font-lock in COMINT modes
Date: Fri, 08 Dec 2006 23:02:29 -0500	[thread overview]
Message-ID: <jwvfybpen6s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <pan.2006.12.09.02.15.49.116482@as.arizona.edu> (JD Smith's message of "Fri\, 08 Dec 2006 19\:15\:50 -0700")

> I haven't understood how a purely nil font-lock-defaults implicitly
> prevents string+comment fontification independent of the keywords-only
> setting, but it does.

Because if it's nil font-lock-mode-internal is not activated at all.
AFAIK nil and (nil t) are equivalent (i.e. don't highlight anything), except
that (nil t) takes a lot more CPU to do nothing (it runs all the
font-lock-foo-function hooks, enables jit-lock so as to do nothing
just-in-time rather than eagerly, checks where nothing needs to be done,
rounds up to a whole number of lines the region upon which inaction is
requested, checks if there's a multiline entity and extends the region even
more, so that nothing is done in a multiline awaer way, ...).


        Stefan

  reply	other threads:[~2006-12-09  4:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  0:57 Font-lock in COMINT modes JD Smith
2006-12-07 16:38 ` JD Smith
2006-12-07 18:00 ` JD Smith
2006-12-09  1:26   ` Richard Stallman
2006-12-09  2:15     ` JD Smith
2006-12-09  4:02       ` Stefan Monnier [this message]
2006-12-11 16:22         ` JD Smith
2006-12-12 14:29           ` Richard Stallman
     [not found]             ` <87vekaf780.fsf@stupidchicken.com>
2006-12-18 16:00               ` Richard Stallman
2006-12-18 16:36                 ` Chong Yidong
2006-12-18 20:38                   ` Stefan Monnier
2006-12-20 13:00                     ` Richard Stallman
2006-12-20 22:06                       ` Stefan Monnier
2006-12-09 18:25       ` Richard Stallman

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=jwvfybpen6s.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    /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).