From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Nested sit-for's Date: Thu, 17 Aug 2006 17:09:12 +0200 Message-ID: References: <87y7tp90i1.fsf@stupidchicken.com> <87hd0bjvoi.fsf@furball.mit.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1155827484 14735 80.91.229.2 (17 Aug 2006 15:11:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 17 Aug 2006 15:11:24 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 17 17:11:18 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 1GDjWN-00071k-Lv for ged-emacs-devel@m.gmane.org; Thu, 17 Aug 2006 17:11:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GDjWM-00021W-PA for ged-emacs-devel@m.gmane.org; Thu, 17 Aug 2006 11:10:58 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GDjWC-00021R-W5 for emacs-devel@gnu.org; Thu, 17 Aug 2006 11:10:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GDjWA-00021E-5g for emacs-devel@gnu.org; Thu, 17 Aug 2006 11:10:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GDjWA-00021B-13 for emacs-devel@gnu.org; Thu, 17 Aug 2006 11:10:46 -0400 Original-Received: from [195.41.46.235] (helo=pfepa.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GDjcd-0005it-8g; Thu, 17 Aug 2006 11:17:27 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (unknown [80.165.4.124]) by pfepa.post.tele.dk (Postfix) with SMTP id 5CC43FAC086; Thu, 17 Aug 2006 17:10:32 +0200 (CEST) Original-To: Chong Yidong In-Reply-To: <87hd0bjvoi.fsf@furball.mit.edu> (Chong Yidong's message of "Thu, 17 Aug 2006 10:14:53 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:58468 Archived-At: Chong Yidong writes: > storm@cua.dk (Kim F. Storm) writes: > >>> It would work to have ONE timer that does sit-for if we make a rule >>> that no others can do so. We could define jit-lock as this one >>> exception. (This has the advantage of not involving any change in the >>> code, just comments and the Lisp Manual.) >> >> I agree with your analysis. >> >> But, IMO, if we make it a rule that timers should generally not use >> sit-for, then a central function like jit-lock should definitely not >> use sit-for! > > If we simply document that "timers (and process filters) should avoid > using sit-for", it should be clear to the reader that rare exceptions > may exist (especially if we add a comment to jit-lock-stealth-fontify > stating this). After the release, we can probably rework > jit-lock-stealth-fontify to avoid using sit-for, but I don't think the > current situation is bad enough to block the release. > > OTOH, I don't remember any other timers or process filters in the > Emacs tree that use a long sit-for or loop waiting for input. Anyone > know of any? [We have discussed this pb before, but never found a solution]. I don't know if it is related, but from time to time (at least a few times daily), the cursor disappears, and doesn't return until I do "something" (e.g. click the mouse or type a key). I use blinking cursor, but when this happens, it typically seems to happen immediately after some event that updates part of the screen (like buffer switching), i.e. not as an effect of first showing the cursor and then "blinking it off". Examples where this happens: 1) returning to the group buffer in Gnus (after closing a summary buffer). [this is where I've seen this most] 2) returning to the summary buffer after responding to an article. But I also think I've seen it hiding the cursor after typing some characters... I don't know if it is related to timers at all, but it seems to happen (marginally) more often now than before the recent sit-for changes ... -- Kim F. Storm http://www.cua.dk