From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
Date: Tue, 28 Nov 2006 12:49:30 -0500 [thread overview]
Message-ID: <E1Gp75G-0006fT-5Y@fencepost.gnu.org> (raw)
In-Reply-To: <456A95B3.2020200@ubin.jp> (message from ishikawa on Mon, 27 Nov 2006 16:37:23 +0900)
It seems that about half the people who posted something about
font-lock-support-mode are aware of jit-lock mode whereas
the other half got stuck with lazy-lock mode. My guess is that people actively
tracking the latest CVS branch (and thus the pretest version)
are well aware of jit-lock mode and the people who have not
bothered with CVS version wrote about lazy-lock vs fast-lock and
have not updated the web pages for some time.
What would people think of making font-lock-support-mode a no-op, and
creating some new variable people can use if they really want to use
something else instead of jit-lock?
next parent reply other threads:[~2006-11-28 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <456152B2.6040307@ubin.jp>
[not found] ` <E1GmQME-0005rp-VJ@fencepost.gnu.org>
[not found] ` <45641140.5050502@ubin.jp>
[not found] ` <E1Gn4h2-00057x-9s@fencepost.gnu.org>
[not found] ` <4566A16F.2030605@ubin.jp>
[not found] ` <E1Go9KM-0006hh-VC@fencepost.gnu.org>
[not found] ` <456A95B3.2020200@ubin.jp>
2006-11-28 17:49 ` Richard Stallman [this message]
2006-11-28 20:58 ` "Use font-lock-support-mode rather than calling lazy-lock-mode" Stefan Monnier
2006-11-29 6:54 ` ishikawa
2006-11-29 16:26 ` Richard Stallman
2006-11-29 18:19 ` Stefan Monnier
2006-11-30 19:48 ` Richard Stallman
2006-12-01 6:29 ` ishikawa
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=E1Gp75G-0006fT-5Y@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).