From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Fwd: overlay face property not used for after-string property Date: Mon, 05 Nov 2007 10:30:02 +0100 Message-ID: <86zlxtdopx.fsf@lola.quinscape.zz> 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 1194255023 11916 80.91.229.12 (5 Nov 2007 09:30:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Nov 2007 09:30:23 +0000 (UTC) Cc: Joe Wells , 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 10:30:27 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 1IoyHm-0003CP-0t for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 10:30:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoyHa-0007l8-U6 for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 04:30:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IoyHX-0007jR-FC for emacs-devel@gnu.org; Mon, 05 Nov 2007 04:30:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IoyHV-0007hd-JP for emacs-devel@gnu.org; Mon, 05 Nov 2007 04:30:07 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoyHV-0007hC-Cp for emacs-devel@gnu.org; Mon, 05 Nov 2007 04:30:05 -0500 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IoyHU-0006BY-Tx for emacs-devel@gnu.org; Mon, 05 Nov 2007 04:30:05 -0500 Original-Received: from quinscape.de (dslnet.212-29-44.ip210.dokom.de [212.29.44.210] (may be forged)) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id KAA00915 for ; Mon, 5 Nov 2007 10:30:02 +0100 X-Delivered-To: Original-Received: (qmail 20415 invoked from network); 5 Nov 2007 09:30:02 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 5 Nov 2007 09:30:02 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 388978F289; Mon, 5 Nov 2007 10:30:02 +0100 (CET) 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/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:82559 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. > > That is not good enough for the final implementation, but it is good > enough for experimenting to find the right criteria. 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. I think that the before-string should, in effect, use (get-char-property (overlay-start ov) 'face) to determine the face to use if no fully specified face is in the before-string. Similarly for after-string. That's simple, clear and straightforward for the user to understand. It also has the "right thing" feeling to it, which ignoring surrounding faces doesn't. -- David Kastrup