From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joe Wells Newsgroups: gmane.emacs.devel Subject: Re: Fwd: overlay face property not used for after-string property Date: Mon, 05 Nov 2007 11:55:32 +0000 Message-ID: <861wb4j497.fsf@macs.hw.ac.uk> References: <86r6jfz3bb.fsf@macs.hw.ac.uk> <86bqaixmxk.fsf@macs.hw.ac.uk> <86bqabjozh.fsf@macs.hw.ac.uk> <86y7ddipg5.fsf_-_@macs.hw.ac.uk> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1194263760 7445 80.91.229.12 (5 Nov 2007 11:56:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Nov 2007 11:56:00 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 05 12:56:04 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ip0Ye-0008P3-Sy for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 12:55:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip0YU-0001Ua-CP for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 06:55:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ip0YR-0001T7-AB for emacs-devel@gnu.org; Mon, 05 Nov 2007 06:55:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ip0YM-0001Qk-EQ for emacs-devel@gnu.org; Mon, 05 Nov 2007 06:55:42 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip0YM-0001Qg-9W for emacs-devel@gnu.org; Mon, 05 Nov 2007 06:55:38 -0500 Original-Received: from izanami.macs.hw.ac.uk ([137.195.13.6]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ip0YJ-00021b-3b; Mon, 05 Nov 2007 06:55:35 -0500 Original-Received: from lxultra1.macs.hw.ac.uk ([137.195.27.173]:35160 helo=127.0.0.1) by izanami.macs.hw.ac.uk with smtp (Exim 4.51) id 1Ip0YH-0003ti-1Y; Mon, 05 Nov 2007 11:55:33 +0000 Original-Received: (nullmailer pid 18231 invoked by uid 1001); Mon, 05 Nov 2007 11:55:32 -0000 In-Reply-To: (Richard Stallman's message of "Mon\, 05 Nov 2007 03\:47\:13 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:82568 Archived-At: Richard Stallman writes: > I think this information may not be enough. I think the policy > would also need to know which of the overlay properties > before-string, display, or after-string the string comes from. > > In most cases you can determine this by looking at the overlay's > properties and seeing where the string appears. That will work except > when the overlay has two properties that contain strings that are eq. This would be a real pain. What if the string being displayed is a display property on the before-string? You have to not just check all 3 of before-string, display, and after-string overlay properties, but you also have to scan through both the before-string and after-string properties looking for display text properties. (By the way, in a separate message, I have complained about a bug that strikes when eq strings are used in distinct display properties.) > That is not good enough for the final implementation, but it is good > enough for experimenting to find the right criteria. I don't think it is good enough even for experimenting, for the reason I indicate above. > If the right > criteria really depend on this information, we can add a mechanism to > provide the information efficiently and reliably. So I see no need to > do that until we know whether it is needed. -- Joe