From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: "Use font-lock-support-mode rather than calling lazy-lock-mode" Date: Tue, 28 Nov 2006 12:49:30 -0500 Message-ID: References: <456152B2.6040307@ubin.jp> <45641140.5050502@ubin.jp> <4566A16F.2030605@ubin.jp> <456A95B3.2020200@ubin.jp> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1164736291 25353 80.91.229.2 (28 Nov 2006 17:51:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 28 Nov 2006 17:51:31 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 28 18:51:30 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gp76v-00052L-Al for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2006 18:51:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gp76v-0006YZ-10 for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2006 12:51:13 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gp75N-0004ow-Br for emacs-devel@gnu.org; Tue, 28 Nov 2006 12:49:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gp75M-0004mb-9K for emacs-devel@gnu.org; Tue, 28 Nov 2006 12:49:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gp75M-0004lP-2L for emacs-devel@gnu.org; Tue, 28 Nov 2006 12:49:36 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gp75J-0003NR-Ok for emacs-devel@gnu.org; Tue, 28 Nov 2006 12:49:34 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.52) id 1Gp75G-0006fT-5Y; Tue, 28 Nov 2006 12:49:31 -0500 Original-To: ishikawa In-reply-to: <456A95B3.2020200@ubin.jp> (message from ishikawa on Mon, 27 Nov 2006 16:37:23 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:62974 Archived-At: 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?