From: Ian Zimmerman <nobrowser@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: lazy-lock vs. jit-lock
Date: Thu, 29 Dec 2005 17:07:59 -0800 (PST) [thread overview]
Message-ID: <87wthn75oy.fsf@gmail.com> (raw)
In-Reply-To: <1135871759.887150.87710@g47g2000cwa.googlegroups.com>
rgb> (setq jit-lock-chunk-size 10000)
This one seems to make the difference - thanks.
The documentation could be improved, I think; it's not clear if this
variable controls fontification of visible or off-screen text,
for example.
--
A true pessimist won't be discouraged by a little success.
next prev parent reply other threads:[~2005-12-30 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.20757.1135839922.20277.help-gnu-emacs@gnu.org>
2005-12-29 7:03 ` lazy-lock vs. jit-lock Ian Zimmerman
2005-12-29 11:10 ` Peter Dyballa
2005-12-29 20:45 ` Eli Zaretskii
[not found] ` <mailman.20768.1135856848.20277.help-gnu-emacs@gnu.org>
2005-12-29 16:34 ` Stefan Monnier
2005-12-29 15:16 ` shreevatsa
2005-12-29 15:54 ` Ian Zimmerman
2005-12-29 15:55 ` rgb
2005-12-30 1:07 ` Ian Zimmerman [this message]
2005-12-30 13:21 ` Eli Zaretskii
2005-12-29 16:39 ` Stefan Monnier
2005-12-29 18:20 ` Ian Zimmerman
2005-12-29 19:18 ` Stefan Monnier
2005-12-29 20:43 ` Eli Zaretskii
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=87wthn75oy.fsf@gmail.com \
--to=nobrowser@gmail.com \
--cc=help-gnu-emacs@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.
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).