From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Default of jit-lock-stealth-time Date: Mon, 26 Feb 2007 14:42:04 +0100 Message-ID: <45E2E3AC.6050300@gmx.at> References: <85tzxazb8r.fsf@lola.goethe.zz> <87ps7x4clj.fsf@pacem.orebokech.com> <85irdpweuq.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1172497504 17860 80.91.229.12 (26 Feb 2007 13:45:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Feb 2007 13:45:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 26 14:44:57 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 1HLg9s-0000yP-I9 for ged-emacs-devel@m.gmane.org; Mon, 26 Feb 2007 14:44:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HLg9s-0002x4-53 for ged-emacs-devel@m.gmane.org; Mon, 26 Feb 2007 08:44:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HLg9h-0002wK-Nd for emacs-devel@gnu.org; Mon, 26 Feb 2007 08:44:41 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HLg9f-0002w8-9v for emacs-devel@gnu.org; Mon, 26 Feb 2007 08:44:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HLg9f-0002w5-42 for emacs-devel@gnu.org; Mon, 26 Feb 2007 08:44:39 -0500 Original-Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.52) id 1HLg9e-0000Nh-IS for emacs-devel@gnu.org; Mon, 26 Feb 2007 08:44:38 -0500 Original-Received: (qmail invoked by alias); 26 Feb 2007 13:44:37 -0000 X-Provags-ID: V01U2FsdGVkX1/DnWNYqDjDpTUB2gGu1RFBKdpn6wG5/0p0qT/jjz NYyQ== User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:66850 Archived-At: > So it seems plain stupid to release it with a setting that will impact > and annoy users and cause a support burden after the release. While I agree with all of David's arguments (and even add the one that a buffer tail is stealthily refontified after every single buffer change followed by 16 secs idleness) I'm afraid that setting this to nil won't remove any support burden. Many major modes still work better when they are allowed to fontify a buffer from beginning to end. Also, when a mode uses font-lock to assign `syntax-table' properties, there's a slight chance that an editing sequence that worked with stealth fontification turned on will not work any more when stealth fontification is turned off. Having fontification assign syntax-table properties is certainly flawed by design but at the moment there's no other way to do that automatically. With other words, setting this to nil may cause some obscure bugs get reported (and hopefully fixed) earlier ... martin, who has stealth fontification turned off ever since