From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: jit-lock refontifies too much Date: Sat, 01 Oct 2005 19:25:53 -0400 Message-ID: References: <43251F5E.9040601@gmx.at> <873boa8l30.fsf-monnier+emacs@gnu.org> <4327B9C9.30406@gmx.at> <87oe6vx4he.fsf-monnier+emacs@gnu.org> <433126E3.1030905@gmx.at> <433254BF.8040205@gmx.at> <87ll1pvwyl.fsf-monnier+emacs@gnu.org> <4336A37C.70002@gmx.at> <43394493.6070805@gmx.at> <433E3BF8.6090700@gmx.at> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1128209755 16858 80.91.229.2 (1 Oct 2005 23:35:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 1 Oct 2005 23:35:55 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 02 01:35:51 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ELqt4-0007Ww-2l for ged-emacs-devel@m.gmane.org; Sun, 02 Oct 2005 01:35:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELqt3-0005sR-Jn for ged-emacs-devel@m.gmane.org; Sat, 01 Oct 2005 19:35:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ELqrM-0005Tt-Ij for emacs-devel@gnu.org; Sat, 01 Oct 2005 19:33:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ELqrJ-0005Rz-4R for emacs-devel@gnu.org; Sat, 01 Oct 2005 19:33:38 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ELqrI-0005QE-9R for emacs-devel@gnu.org; Sat, 01 Oct 2005 19:33:36 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ELqjq-0000qn-Q4 for emacs-devel@gnu.org; Sat, 01 Oct 2005 19:25:54 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1ELqjp-0006hk-P5; Sat, 01 Oct 2005 19:25:53 -0400 Original-To: martin rudalics In-reply-to: <433E3BF8.6090700@gmx.at> (message from martin rudalics on Sat, 01 Oct 2005 09:34:16 +0200) 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:43442 Archived-At: I somewhat fell between two stools here. With respect to my first proposal Stefan judged ".. yet-another-text-property is a waste of precious CPU and memory resources." I do not necessarily agree with him; I think it would depend on how much good the feature does. I am not sure how much good it would do, so I don't know whether this idea is worth while. > It means "the before and after ppss values do not match". > > You're arguing this can't happen very easily. Maybe that is true. > I didn't argue that. Complete ppss are hardly ever "in sync" after a modification of preceding text. The values of ppss I need to determine whether context changed might be in sync quite often. "In sync" doesn't mean entirely equal, it means that they show there was no relevant change. By the way, in principle we could add more info to the ppss value so that font lock gets whatever info it needs so as to work correctly.