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: feature request: text property to prevent font-locking Date: Tue, 02 Sep 2014 08:04:14 +0200 Organization: Organization?!? Message-ID: <877g1m1rtt.fsf@fencepost.gnu.org> References: <20140830092701.GA3351@acm.acm> <34f3e246-bbfb-4864-83e9-4a0c81d4202e@default> <0f746243-e04c-4d07-ace8-2e54625aaffc@default> <20140831214324.GB4401@acm.acm> <87lhq49l3v.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1409637906 15345 80.91.229.3 (2 Sep 2014 06:05:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Sep 2014 06:05:06 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 02 08:04:59 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 1XOhD6-0002xe-Hq for ged-emacs-devel@m.gmane.org; Tue, 02 Sep 2014 08:04:56 +0200 Original-Received: from localhost ([::1]:36000 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOhD6-0002sG-5Z for ged-emacs-devel@m.gmane.org; Tue, 02 Sep 2014 02:04:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54454) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOhCm-0002s4-MY for emacs-devel@gnu.org; Tue, 02 Sep 2014 02:04:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOhCg-000475-5Z for emacs-devel@gnu.org; Tue, 02 Sep 2014 02:04:36 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:50652) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOhCf-00046w-V1 for emacs-devel@gnu.org; Tue, 02 Sep 2014 02:04:30 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XOhCd-0002hH-Q7 for emacs-devel@gnu.org; Tue, 02 Sep 2014 08:04:27 +0200 Original-Received: from x2f4cf01.dyn.telefonica.de ([2.244.207.1]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Sep 2014 08:04:27 +0200 Original-Received: from dak by x2f4cf01.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Sep 2014 08:04:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f4cf01.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Cancel-Lock: sha1:8C6IsSxGPsBuLIg5zTRzMaouY/k= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:173945 Archived-At: Richard Stallman writes: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Overlays are not the same as extents. Extents try to be both > text properties and overlays, and I think that mixture can't > be implemented without incoherent behaviors. I'm not complete sure whether extents can or cannot cover all use cases of overlays/properties: it was some time since I last looked. The main problem I had when working with them is that the purported generality is elusive since part of the difference in Emacs' semantics of overlays and text properties is encoded in extent properties while other parts are encoded in the parameters you pass to the subroutines for accessing extents. The result is that the complexity for a particular application tends to bleed all over the place whenever you don't restrict yourself to the Emacs abstractions, most easily done by using compatibility functions. However, there is no point in Emacs not supporting overlay and text properties identically whenever a particular property is not inherently tied to the difference between overlay and text properties. I definitely remember being annoyed in the past by some properties requiring the use of one and not the other. But I don't remember the details right now. Having the same underlying implementation for overlays and text properties is of course a reliable way to have the same supported set of properties by default. -- David Kastrup