From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Default of jit-lock-stealth-time Date: Tue, 27 Feb 2007 22:54:27 +0200 Message-ID: References: <85tzxazb8r.fsf@lola.goethe.zz> <87ps7x4clj.fsf@pacem.orebokech.com> <85irdpweuq.fsf@lola.goethe.zz> <87ejocik1a.fsf@catnip.gol.com> <85hct8ovog.fsf@lola.goethe.zz> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1172609702 31421 80.91.229.12 (27 Feb 2007 20:55:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 27 Feb 2007 20:55:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 27 21:54:52 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HM9LJ-0005MY-M8 for ged-emacs-devel@m.gmane.org; Tue, 27 Feb 2007 21:54:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HM9LJ-00041P-Hf for ged-emacs-devel@m.gmane.org; Tue, 27 Feb 2007 15:54:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HM9L9-00041K-36 for emacs-devel@gnu.org; Tue, 27 Feb 2007 15:54:27 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HM9L7-000418-Mn for emacs-devel@gnu.org; Tue, 27 Feb 2007 15:54:26 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HM9L7-000415-KS for emacs-devel@gnu.org; Tue, 27 Feb 2007 15:54:25 -0500 Original-Received: from romy.inter.net.il ([213.8.233.24]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HM9L3-0004iG-Kw; Tue, 27 Feb 2007 15:54:22 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-163-35.inter.net.il [80.230.163.35]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id HGD84442 (AUTH halo1); Tue, 27 Feb 2007 22:54:22 +0200 (IST) In-reply-to: <85hct8ovog.fsf@lola.goethe.zz> (message from David Kastrup on Tue, 27 Feb 2007 09:23:59 +0100) X-detected-kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) 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:66951 Archived-At: > Cc: Miles Bader , Eli Zaretskii , > emacs-devel@gnu.org > From: David Kastrup > Date: Tue, 27 Feb 2007 09:23:59 +0100 > > Stefan Monnier writes: > > > Sure. Jit-lock-stealth has been in wide use since Emacs-21.1 (and > > the years of development before), so it's clear that its bad effects > > are sufficiently mild. > > Font-lock was turned off by default in versions 21.1 to 21.4 since its > performance impact was not well-behaved enough. Inaccurate. First, font-lock was turned off by default in _all_ versions of Emacs since its introduction (in v19.x, AFAIR). More importantly, a large majority of users turned it on, so that jit-lock-stealth _was_, indeed, widely used since v21.1, where jit-lock was introduced. > Quite a bit of fixes went into font-lock in order to make it a > defensible choice to enable it by default. Inaccurate. Improvements to jit-lock notwithstanding, the main reason for turning it on was that we decided the garden-variety CPUs are nowadays fast enough to fontify buffers without annoyance to most users.