From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Layered display API Date: Fri, 15 Aug 2014 05:20:12 +0400 Message-ID: <53ED604C.8020705@yandex.ru> References: <86tx5r7l1j.fsf@yandex.ru> <53E097F7.5050407@gmx.at> <53E0ABF9.7070506@yandex.ru> <8338dbqcai.fsf@gnu.org> <53E14AF4.6050804@yandex.ru> <83k36mpbxg.fsf@gnu.org> <53E22245.4070307@yandex.ru> <8361i5pmch.fsf@gnu.org> <53E294BD.1000500@yandex.ru> <837g2knwb2.fsf@gnu.org> <53E818F0.2080104@yandex.ru> <8361hzjciv.fsf@gnu.org> <53EAD0B1.1010405@yandex.ru> <83iolwif2l.fsf@gnu.org> <53EC205F.7030801@yandex.ru> <8361hvixxz.fsf@gnu.org> <53ECB5C3.20309@yandex.ru> <834mxfhzd4.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1408065652 23447 80.91.229.3 (15 Aug 2014 01:20:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Aug 2014 01:20:52 +0000 (UTC) Cc: rudalics@gmx.at, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 15 03:20:41 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XI6C9-0000pt-BC for ged-emacs-devel@m.gmane.org; Fri, 15 Aug 2014 03:20:41 +0200 Original-Received: from localhost ([::1]:57026 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XI6C8-0002UA-Nu for ged-emacs-devel@m.gmane.org; Thu, 14 Aug 2014 21:20:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XI6Bw-0002U0-Ai for emacs-devel@gnu.org; Thu, 14 Aug 2014 21:20:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XI6Bn-0002Tr-7K for emacs-devel@gnu.org; Thu, 14 Aug 2014 21:20:28 -0400 Original-Received: from mail-lb0-x235.google.com ([2a00:1450:4010:c04::235]:60963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XI6Bm-0002Th-UV; Thu, 14 Aug 2014 21:20:19 -0400 Original-Received: by mail-lb0-f181.google.com with SMTP id 10so1442188lbg.40 for ; Thu, 14 Aug 2014 18:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GfOzgLIKEKhKwBp2i6OhCfNFE5Dy2VC8VcDZMGbWGf0=; b=SKPR5mRI75fI9ki9rMUhY2Bol33Q9v8G3iWz7XMMAIxZj4oplAhXxwKTFM8bNMBqCG B5ouscBzSOTUgE1wuBuBYgZzlY8LlBF1EnlSPTFP1Ha+BD+Y4C8Dp1651zCtGsLl/pn9 n/U9xnp775nuPeBEJ4AQ9prclA5LKcJMz0AyWDJczoIF+pTQCKyvywxKHFX0qoIB7/Qp dATzopjqlCJSWPq/hrl1Y4d5iLI7TkRBjQHdPxE0N2rKv4FTEYTPJosRuvJQ/thVEmAP AbjpChaXed0OLAC9NT0iFy4Yeb4svdnp+i6dNHHXWDDch1yGWTKtQgamGfvNh1fjXcVR EkLw== X-Received: by 10.112.40.161 with SMTP id y1mr8698011lbk.61.1408065617205; Thu, 14 Aug 2014 18:20:17 -0700 (PDT) Original-Received: from [192.168.1.3] ([178.252.98.87]) by mx.google.com with ESMTPSA id g7sm4041234laa.35.2014.08.14.18.20.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Aug 2014 18:20:16 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 In-Reply-To: <834mxfhzd4.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:173679 Archived-At: On 08/14/2014 07:20 PM, Eli Zaretskii wrote: >> Doesn't any overlay's `display' get priority over text's `display'? > > I don't remember, but if it does, it's an implementation detail > subject to change without notice. ... > This property we are discussing (that doesn't yet exist) will be acted > upon by the display engine. The display engine always knows what > "things" are there at point, and the supporting logic for this > property will cause the display engine to ignore all the other > "things" and display only the overlay that has this property. At > least that's the theory. Well, since we don't only need to replace the displayed characters, but also modify them, this doesn't do a lot of work for us. From what I understand, you're suggesting a property that would act like a combination of overlay + display does currently. Why not just document that current behavior and then stick to it, rather than introduce the new property?