From: Alan Mackenzie<none@example.invalid>
Subject: Re: What is the _essential_ difference between lazy-lock and jit-lock?
Date: Fri, 23 Jan 2004 22:34:59 +0000 [thread overview]
Message-ID: <ji7sub.5g.ln@acm.acm> (raw)
In-Reply-To: mailman.1214.1074858619.928.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@elta.co.il> wrote on Fri, 23 Jan 2004 13:42:53 +0200:
>> From: Alan Mackenzie<none@example.invalid>
>> 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).
Any chance of a revision number (presumably of jit-lock.el) where this
was fixed?
> Please try again and see if you still have such problems.
I've set font-lock-support-mode back to jit-, and I've been trying all
evening ;-) With Emacs 21.1, I've had my Emacs lock up just once.
Loading jit-lock.elc V1.31 (the latest from savannah), I've not triggered
the problem. Not yet. I'll try loading a few more buffers to see if
that makes things worse.
[ .... ]
>> 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.
I wasn't meaning to suggest that they should be removed. Merely that
they should be supplemented with a more handy higher level tool, leaving
the individual options available for specific needs/wants.
> Perhaps you want to say that their documentation needs some work--that
> is something I could understand.
That too.
--
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").
next prev parent reply other threads:[~2004-01-23 22:34 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
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 [this message]
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=ji7sub.5g.ln@acm.acm \
--to=none@example.invalid \
/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).