unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: font-lock-maximum-size
Date: Mon, 17 Oct 2011 14:00:03 +0000	[thread overview]
Message-ID: <20111017140003.GA4735@acm.acm> (raw)
In-Reply-To: <8762joynza.fsf@gnu.org>

Hi, Yidong.

On Mon, Oct 17, 2011 at 05:19:21AM -0400, Chong Yidong wrote:
>   font-lock-maximum-size is a variable defined in `font-lock.el'.
>   Its value is 256000

>   Documentation:
>   Maximum size of a buffer for buffer fontification.
>   Only buffers less than this can be fontified when Font Lock mode is
>   turned on.

> Looks like this variable doesn't work, and hasn't worked for a long
> time.  It nothing when JIT lock mode is in use, and since fast-lock and
> lazy-lock are obsolete, it's pretty useless.  (Anyway, source files
> larger than 250K are not uncommon.)

Doesn't it work when no font-lock-support-mode is in operation?

> If there are no objections, I am going to mark it as deprecated, and
> remove it from the manual.

I don't object - even if it were still operational, modern PCs are so
fast now that f-l-max-size would have to be so big to be sensible that it
would exceed the size of nearly all source code buffers.

However, please don't ever downplay the usefulness of (eq
f-l-support-mode nil).  This is very useful for debugging f-l-keywords,
etc., and also works well when jit-lock doesn't - I've had quite a few
problems with font lock over the years, many of them being caused by a
jit-lock chunk starting in the middle of a (largish) syntactical
construct.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2011-10-17 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17  9:19 font-lock-maximum-size Chong Yidong
2011-10-17 14:00 ` Alan Mackenzie [this message]
2011-10-17 15:30 ` font-lock-maximum-size Stefan Monnier
2011-10-18  3:11   ` font-lock-maximum-size Chong Yidong

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=20111017140003.GA4735@acm.acm \
    --to=acm@muc.de \
    --cc=cyd@gnu.org \
    --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).