unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: What is the _essential_ difference between lazy-lock and	jit-lock?
Date: Fri, 23 Jan 2004 13:42:53 +0200	[thread overview]
Message-ID: <3405-Fri23Jan2004134252+0200-eliz@elta.co.il> (raw)
In-Reply-To: <vetqub.q5.ln@acm.acm> (message from Alan Mackenzie on Fri, 23 Jan 2004 10:36:15 +0000)

> From: Alan Mackenzie<none@example.invalid>
> Newsgroups: gnu.emacs.help
> Date: Fri, 23 Jan 2004 10:36:15 +0000
> 
> > There's nothing to debug: it's normal, well-understood behavior.
> > Better yet: it's done on purpose.
> 
> Surely not - Emacs _HUNG_ with stealth fontification, accepting no keypresses
> (apart from a double C-g), and remained in this state overnight (> 8
> hours).

I think these problems were solved in the meantime (IIRC, they were
due to bad interaction between JIT lock and font-lock definitions for
some modes).  Please try again and see if you still have such
problems.

> Tuning jit-lock is very difficult.  Using customize, even after finding
> the Jit Lock customize group (difficult in itself), there is a
> bewildering collection of options to set.  (I mean here bewildering to
> _me_, and I think I have a better grasp of font lock than typical Emacs
> users.)  It would seem that a detailed understanding of how jit-lock
> works is a prerequisite for setting these options intelligently.  This is
> surely not a good thing.
> 
> Perhaps what is wanted is a command like `(font-lock-tune-font-lock
> 'low-powered-workstation)' by which users could select from amongst
> several pre-defined tunings, somewhat analogous to CC Mode's
> `c-set-style'.

I have a better idea of a user interface:

        (font-lock-tune-font-lock 'my-specific-preferences)
or
	(font-lock-tune-font-lock 'my-favorite-computer)

Seriously, though: that's the first time I hear an Emacs veteran
complain about too many customization options.  Surely, you should
know that they all exist for a good purpose.  Perhaps you want to say
that their documentation needs some work--that is something I could
understand.

  reply	other threads:[~2004-01-23 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 18:06 What is the _essential_ difference between lazy-lock and jit-lock? Alan Mackenzie
2004-01-22 18:57 ` Stefan Monnier
2004-01-22 23:07   ` Alan Mackenzie
2004-01-22 23:37     ` Stefan Monnier
2004-01-23 10:36       ` Alan Mackenzie
2004-01-23 11:42         ` Eli Zaretskii [this message]
2004-01-23 16:29         ` Stefan Monnier
2004-01-23 19:28           ` Kevin Rodgers
2004-01-26 19:03           ` Alan Mackenzie
2004-01-26 21:46             ` Stefan Monnier
     [not found]         ` <mailman.1214.1074858619.928.help-gnu-emacs@gnu.org>
2004-01-23 22:34           ` Alan Mackenzie
2004-01-24 10:41             ` Eli Zaretskii
     [not found]             ` <mailman.1266.1074941164.928.help-gnu-emacs@gnu.org>
2004-01-26 17:53               ` Alan Mackenzie

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=3405-Fri23Jan2004134252+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    /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).