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: Tue, 06 Nov 2007 03:19:20 +0000 Message-ID: <86pryof4cn.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> <86zlxtdopx.fsf@lola.quinscape.zz> <86640gj4fx.fsf@macs.hw.ac.uk> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1194319192 25069 80.91.229.12 (6 Nov 2007 03:19:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Nov 2007 03:19:52 +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 Tue Nov 06 04:19:54 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 1IpEyl-0006JM-62 for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2007 04:19:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpEyZ-0002QM-Rf for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 22:19:39 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpEyW-0002Oo-Ij for emacs-devel@gnu.org; Mon, 05 Nov 2007 22:19:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpEyT-0002Nk-KS for emacs-devel@gnu.org; Mon, 05 Nov 2007 22:19:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpEyT-0002NO-ER for emacs-devel@gnu.org; Mon, 05 Nov 2007 22:19:33 -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 1IpEyL-00006g-1R; Mon, 05 Nov 2007 22:19:25 -0500 Original-Received: from lxultra1.macs.hw.ac.uk ([137.195.27.173]:49960 helo=127.0.0.1) by izanami.macs.hw.ac.uk with smtp (Exim 4.51) id 1IpEyG-00084B-7g; Tue, 06 Nov 2007 03:19:20 +0000 Original-Received: (nullmailer pid 3002 invoked by uid 1001); Tue, 06 Nov 2007 03:19:20 -0000 In-Reply-To: (Richard Stallman's message of "Mon\, 05 Nov 2007 21\:15\:58 -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:82621 Archived-At: Richard Stallman writes: > I would like to strongly suggest that overlay before-string, > display, and after-string properties should *not* be affected by > the text-property face properties in the buffer. > > That would be easy to implement, but it seems to me that in some > cases text properties should influence these strings, just as region > highlighting should. How about negative overlay priorities for this? (I assume you mean =E2=80=9Ctext properties in the buffer=E2=80=9D, as the = phrase =E2=80=9Ctext properties=E2=80=9D includes text properties in the strings.) > Since various features use overlays to do something analogous to > region highlighting, that suggests that in SOME cases we do want one > overlay's faces to affect the strings provided by another overlay, as > you asked for recently. Indeed. > A study of the interaction of those features Maybe collect a list of all the authors of code that uses overlays heavily and CC them on this discussion? :-) > with something like linum might make it possible to figure out some > good rules for such interaction. By the way (a slight shift of topic here), I think the overlays used by linum.el should *not* be affected by the active region face. I think we already discussed this in the e-mail thread on linum.el and the idea was to solve this by giving the active region face a numeric priority (e.g., something like 100 or so) and overlays with higher priority would not be affected. (Has this been done already?) --=20 Joe