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: [rudalics@gmx.at: Re: jit lock sit-for provokes redisplay provokes imenu] Date: Wed, 30 Aug 2006 20:29:40 +0200 Message-ID: <44F5D914.3020604@gmx.at> References: <8764gcde3n.fsf@stupidchicken.com> <878xl754fy.fsf@furball.mit.edu> NNTP-Posting-Host: main.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 1156962654 15467 80.91.229.2 (30 Aug 2006 18:30:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 30 Aug 2006 18:30:54 +0000 (UTC) Cc: Chong Yidong , monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 30 20:30:49 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 1GIUpb-0001lw-RV for ged-emacs-devel@m.gmane.org; Wed, 30 Aug 2006 20:30:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GIUpa-0002WS-HA for ged-emacs-devel@m.gmane.org; Wed, 30 Aug 2006 14:30:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GIUpI-0002WB-7q for emacs-devel@gnu.org; Wed, 30 Aug 2006 14:30:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GIUpG-0002Vf-Qr for emacs-devel@gnu.org; Wed, 30 Aug 2006 14:30:11 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GIUpG-0002Vc-Ji for emacs-devel@gnu.org; Wed, 30 Aug 2006 14:30:10 -0400 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1GIUyi-00025K-C7 for emacs-devel@gnu.org; Wed, 30 Aug 2006 14:39:56 -0400 Original-Received: (qmail invoked by alias); 30 Aug 2006 18:30:08 -0000 Original-Received: from N759P004.adsl.highway.telekom.at (EHLO [62.47.38.196]) [62.47.38.196] by mail.gmx.net (mp035) with SMTP; 30 Aug 2006 20:30:08 +0200 X-Authenticated: #14592706 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en Original-To: rms@gnu.org In-Reply-To: X-Y-GMX-Trusted: 0 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:59125 Archived-At: > Stefan wrote: > > This only eliminates one particular source of unwanted updates. I don't > think this code is worth the trouble. > > That cause of unwanted updates is the only one we know of. Nothing > else is likely to change the buffer in the background. `jit-lock-fontify-now' during scrolling, searching, window resizing. Not mentioning the plethora of "hidden buffer changes" in c-mode. > Better yet, introduce a macro `with-buffer-unmodified' like the one used in > jit-lock, and make it manage a `buffer-really-modified-tick', kind of like > the buffer-chars-modified-tick. Then use it in jit-lock/font-lock > and friends. > > That seems a lot more trouble, and I don't see that it is needed. I think it is needed.