all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: lazy-lock vs. jit-lock
Date: Thu, 29 Dec 2005 12:10:29 +0100	[thread overview]
Message-ID: <c75879e93104f72e99b8b8846b1fcc2d@Web.DE> (raw)
In-Reply-To: <877j9otmem.fsf@gmail.com>


Am 29.12.2005 um 08:03 schrieb Ian Zimmerman:

> Can anyone comment on the relative advantages of these kinds of
> font-locking?  jit-lock seems to be the default in Emacs 21.4, but I
> fount that in some buffers (not necessarily large ones) whole chunks 
> are
> left unfontified.  Waiting for them to be "stealthily" fontified also
> doesn't help; only font-lock-fontify-buffer does.
>

jit means just in time -- since modern CPUs are so fast, jit-lock is 
too slow. I think that's jit-lock's story: being helpful on slow 
computers. I seem to remember that it was recommended not to use 
jit-lock any more because it could be removed some day. (I too switched 
off jit-lock some months or years ago.)

--
Greetings

   Pete      <\
              _\     O  _
             |o \  _\\_/-\='
_____________(_)|-(_)  (_)___________________________________

  reply	other threads:[~2005-12-29 11:10 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=c75879e93104f72e99b8b8846b1fcc2d@Web.DE \
    --to=peter_dyballa@web.de \
    --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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.