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: jit lock sit-for provokes redisplay provokes imenu Date: Wed, 26 Jul 2006 18:16:40 +0200 Message-ID: <44C79568.3020305@gmx.at> References: <81CCA6588E60BB42BE68BD029ED4826008838221@wimex2.wim.midas-kapiti.com> <44C0EA68.40105@gmx.at> <44C1EE07.3080502@gmx.at> <44C750EC.2020004@gmx.at> 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 1153930705 4154 80.91.229.2 (26 Jul 2006 16:18:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 26 Jul 2006 16:18:25 +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 Wed Jul 26 18:18:22 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 1G5m4w-0005mu-3q for ged-emacs-devel@m.gmane.org; Wed, 26 Jul 2006 18:17:46 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G5m4v-0002eG-GT for ged-emacs-devel@m.gmane.org; Wed, 26 Jul 2006 12:17:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G5m4D-00024C-SE for emacs-devel@gnu.org; Wed, 26 Jul 2006 12:17:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G5m4B-000209-3k for emacs-devel@gnu.org; Wed, 26 Jul 2006 12:17:00 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G5m4A-0001zu-TA for emacs-devel@gnu.org; Wed, 26 Jul 2006 12:16:58 -0400 Original-Received: from [213.165.64.21] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1G5m5k-0004nj-5l for emacs-devel@gnu.org; Wed, 26 Jul 2006 12:18:36 -0400 Original-Received: (qmail invoked by alias); 26 Jul 2006 16:16:57 -0000 Original-Received: from N825P021.adsl.highway.telekom.at (EHLO [62.47.47.21]) [62.47.47.21] by mail.gmx.net (mp041) with SMTP; 26 Jul 2006 18:16:57 +0200 X-Authenticated: #14592706 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en Original-To: Stefan Monnier 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:57665 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'? I probably don't understand the latter correctly - presumably they could try to do something special for the case BUF_SAVE_MODIFF > BUF_MODIFF because that _would_ indicate a wrap-around. Apparently, there never was a problem but maybe I'm completely wrong here.