From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: jit lock sit-for provokes redisplay provokes imenu Date: Thu, 27 Jul 2006 10:35:26 -0400 Message-ID: References: <81CCA6588E60BB42BE68BD029ED4826008838221@wimex2.wim.midas-kapiti.com> <44C0EA68.40105@gmx.at> <44C1EE07.3080502@gmx.at> <44C750EC.2020004@gmx.at> <44C79568.3020305@gmx.at> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1154010967 9363 80.91.229.2 (27 Jul 2006 14:36:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 27 Jul 2006 14:36:07 +0000 (UTC) Cc: simon.marshall@misys.com, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 27 16:35:54 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 1G66xa-0003fK-Px for ged-emacs-devel@m.gmane.org; Thu, 27 Jul 2006 16:35:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G66xZ-0004iT-UZ for ged-emacs-devel@m.gmane.org; Thu, 27 Jul 2006 10:35:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G66xP-0004i8-EF for emacs-devel@gnu.org; Thu, 27 Jul 2006 10:35:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G66xM-0004hk-ML for emacs-devel@gnu.org; Thu, 27 Jul 2006 10:35:23 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G66xM-0004hh-Co for emacs-devel@gnu.org; Thu, 27 Jul 2006 10:35:20 -0400 Original-Received: from [209.226.175.97] (helo=tomts40-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G66z6-00052C-DT; Thu, 27 Jul 2006 10:37:08 -0400 Original-Received: from localhost ([70.55.146.79]) by tomts40-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060727143516.OZQC24981.tomts40-srv.bellnexxia.net@localhost>; Thu, 27 Jul 2006 10:35:16 -0400 Original-Received: by localhost (Postfix, from userid 20848) id C0F1D8273; Thu, 27 Jul 2006 10:35:26 -0400 (EDT) Original-To: martin rudalics In-Reply-To: <44C79568.3020305@gmx.at> (martin rudalics's message of "Wed, 26 Jul 2006 18:16:40 +0200") 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:57677 Archived-At: >>> return BUF_SAVE_MODIFF (buf) < BUF_CHARS_MODIFF (buf) ? Qt : Qnil; >> Isn't this vulnerable to problems when MODIFF wraps around? > Hmmm... Do you think it's more vulnerable than `buffer-modified-p' or > `update_menu_bar'? Hmm... good point. I just assumed that buffer-modified-p used "!=" instead of "<", but indeed it uses "<" which makes it vulnerable as well. I guess wraparounds are sufficiently unlikely, then. Stefan