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: Sat, 24 Jan 2004 12:41:32 +0200	[thread overview]
Message-ID: <7137-Sat24Jan2004124131+0200-eliz@elta.co.il> (raw)
In-Reply-To: <ji7sub.5g.ln@acm.acm> (message from Alan Mackenzie on Fri, 23 Jan 2004 22:34:59 +0000)

> From: Alan Mackenzie<none@example.invalid>
> Newsgroups: gnu.emacs.help
> Date: Fri, 23 Jan 2004 22:34:59 +0000
> 
> > 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?

Sorry, no.  And the changes were not in jit-lock.el per se, IIRC, but
rather in the font-lock definitions of several modes.

> > 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.

I was only semi-humorous when I suggested that Emacs should itself
know about my own preferences.  If we could have that, it would be a
great UI.

However, in practice, this is next to impossible, and so, IMHO, is
your suggestion.  In the specific case in point, that of tuning JIT
lock, too many factors are specific to the peculiarities of the
individual setup of the machine on which it runs.

Instead of wasting effort to invent a tool that will certainly fail in
a large proportion of cases, Emacs lets you tune the feature with a
set of settings.  The documentation of those settings should make it
clear which ones to use in each particular case.  Perhaps if you could
describe the process that you went through when you tried to figure
out what options to change, we could identify what needs to be
improved in the documentation, or perhaps how to change the set of the
options itself.

  reply	other threads:[~2004-01-24 10:41 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
2004-01-24 10:41             ` Eli Zaretskii [this message]
     [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=7137-Sat24Jan2004124131+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).