From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: Three strikes them out Date: Sat, 31 May 2008 13:58:58 +0200 Message-ID: <48413D82.9080304@gmail.com> References: <48403C07.5080404@gmail.com> <484113E8.1040008@gmail.com> <4841177E.8020708@gmx.at> <484118F0.2050805@gmail.com> <48412778.7030302@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1212235158 7409 80.91.229.12 (31 May 2008 11:59:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 May 2008 11:59:18 +0000 (UTC) Cc: Stefan Monnier , Emacs Devel To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 31 13:59:59 2008 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 1K2Pkb-00076u-14 for ged-emacs-devel@m.gmane.org; Sat, 31 May 2008 13:59:57 +0200 Original-Received: from localhost ([127.0.0.1]:44315 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K2Pjp-0000Hl-Ab for ged-emacs-devel@m.gmane.org; Sat, 31 May 2008 07:59:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K2Pjk-0000HZ-Uz for emacs-devel@gnu.org; Sat, 31 May 2008 07:59:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K2Pjj-0000HK-Ji for emacs-devel@gnu.org; Sat, 31 May 2008 07:59:04 -0400 Original-Received: from [199.232.76.173] (port=37072 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K2Pjj-0000HH-DY for emacs-devel@gnu.org; Sat, 31 May 2008 07:59:03 -0400 Original-Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212]:51284) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K2Pjj-00033Q-8R for emacs-devel@gnu.org; Sat, 31 May 2008 07:59:03 -0400 Original-Received: from c83-254-145-59.bredband.comhem.se ([83.254.145.59]:59871 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1K2Pjg-0002td-5z; Sat, 31 May 2008 13:59:01 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: <48412778.7030302@gmx.at> X-Antivirus: avast! (VPS 080531-0, 2008-05-31), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.145.59 X-Scan-Result: No virus found in message 1K2Pjg-0002td-5z. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1K2Pjg-0002td-5z 15e40655bcb00e826debbf5a9a70b19c X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) 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:98128 Archived-At: martin rudalics wrote: > > What happens when you set `jit-lock-context-time' to a very large value? > > > > I can dig up one of those cases that loops and try it, but why do you > > propose that? (It might of course help a bit to find out where the > > problem happens and I have one case where this could indeed be > > interesting, but I am not sure if that is what you mean.) > > If font-lock loops within contextual refontification there's either a > bug in font-lock (which I consider highly impropable) or there's a bug > in your code (maybe some function called by a hook or another timer) > that changes the buffer and re-triggers contextual refontification. > Whatever applies should be resolved. Thanks. The situation is a bit different in my case, but it could perhaps be that contextual refontificaion is re-triggered. Could that happen when the code runs under font-lock and only text properties and overlays are changed? > > The general problem that looping in a timer may hang Emacs is what I > > really wanted to address here. > > You can't: As soon as you manage to exit looping, a repeating idle timer > will fire again. Yes, that was why I suggested that we implement something that allows us to stop this (with for example C-g C-g C-g).