From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Default of jit-lock-stealth-time Date: Mon, 05 Mar 2007 08:18:22 +0100 Message-ID: <86zm6srwe9.fsf@lola.quinscape.zz> References: <85tzxazb8r.fsf@lola.goethe.zz> <85irdi1mar.fsf@lola.goethe.zz> <85abytkugj.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1173079189 18417 80.91.229.12 (5 Mar 2007 07:19:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 5 Mar 2007 07:19:49 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 05 08:19:43 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 1HO7Ty-0005BL-S8 for ged-emacs-devel@m.gmane.org; Mon, 05 Mar 2007 08:19:43 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HO7Ty-0004zf-BE for ged-emacs-devel@m.gmane.org; Mon, 05 Mar 2007 02:19:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HO7So-0003yg-IN for emacs-devel@gnu.org; Mon, 05 Mar 2007 02:18:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HO7Sm-0003wH-0b for emacs-devel@gnu.org; Mon, 05 Mar 2007 02:18:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HO7Sl-0003wC-6s for emacs-devel@gnu.org; Mon, 05 Mar 2007 02:18:27 -0500 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HO7Sk-0002Pd-H8 for emacs-devel@gnu.org; Mon, 05 Mar 2007 02:18:26 -0500 Original-Received: from quinscape.de (pd95b0fdb.dip0.t-ipconnect.de [217.91.15.219]) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id IAA27530 for ; Mon, 5 Mar 2007 08:18:18 +0100 X-Delivered-To: Original-Received: (qmail 22790 invoked from network); 5 Mar 2007 07:18:23 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 5 Mar 2007 07:18:23 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id BEA9323889; Mon, 5 Mar 2007 08:18:22 +0100 (CET) In-Reply-To: (Richard Stallman's message of "Sun\, 04 Mar 2007 21\:55\:19 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 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:67353 Archived-At: Richard Stallman writes: > So yes, there is likely a bug (or whatever one may call something that > takes up too much time) in this particularly severe case, but it is > not triggered outside of stealth fontification, and stealth > fontification makes the problem be pretty much impossible to debug > properly, and triggers it when editing _any_ buffer. > > Is the bug in font-latex, perhaps? I think it imprudent to call it "the bug": any problem in font highlighting patterns in any of the loaded buffers/major modes can have the same, non-traceable effects. I already said that I have seen similar things with cc-mode. Until we can guarantee that all major modes have efficient font lock patterns/code ("correct" alone does not cut it), stealth fontification will hide problems while making them more severe. After some back and forth with one AUCTeX developer, I have asked him to install a private branch to font-latex which is likely related to the problem seen with texbook.tex. It would be my guess that it might address the particular performance problem seen with texbook.tex. So the problem triggered by this particular input file might be gone with future releases of AUCTeX. But as I already stated: this was merely the file that broke the camel's back for me and caused me to report the problem which I was unable to trace to a cause (stealth fontification _is_ stealthy in hiding its tracks, if not its effects). And it certainly was not the file that caused several other developers to disable stealth fontification before (which they then reported). -- David Kastrup