From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Colin Walters Newsgroups: gmane.emacs.devel Subject: Re: Question about copy-region-as-kill Date: 06 Apr 2002 23:41:06 -0500 Sender: emacs-devel-admin@gnu.org Message-ID: <1018154466.4269.11.camel@space-ghost> References: <87ofh09xjq.fsf@alice.dynodns.net> <200204050602.g3562Dl18586@aztec.santafe.edu> <87bscx7rlf.fsf@alice.dynodns.net> <200204061732.g36HWSb19584@aztec.santafe.edu> <87k7rkmuk0.fsf@alice.dynodns.net> <87zo0gbfb2.fsf@emacswiki.org> <1018138376.27236.49.camel@space-ghost> <87bscwe36t.fsf@tc-1-100.kawasaki.gol.ne.jp> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1018155079 9735 127.0.0.1 (7 Apr 2002 04:51:19 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 7 Apr 2002 04:51:19 +0000 (UTC) Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16u4e6-0002Wu-00 for ; Sun, 07 Apr 2002 06:51:18 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 16u4rs-00030i-00 for ; Sun, 07 Apr 2002 07:05:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16u4dw-0002Us-00; Sat, 06 Apr 2002 23:51:08 -0500 Original-Received: from monk.debian.net ([216.185.54.61] helo=monk.verbum.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16u4d9-0002TK-00 for ; Sat, 06 Apr 2002 23:50:19 -0500 Original-Received: from space-ghost.verbum.private (freedom.cis.ohio-state.edu [164.107.60.183]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "space-ghost.verbum.org", Issuer "monk.verbum.org" (verified OK)) by monk.verbum.org (Postfix (Debian/GNU)) with ESMTP id BF308740009E for ; Sat, 6 Apr 2002 23:50:03 -0500 (EST) Original-Received: by space-ghost.verbum.private (Postfix (Debian/GNU), from userid 1000) id DAB3D982A27; Sat, 6 Apr 2002 23:41:06 -0500 (EST) Original-To: emacs-devel@gnu.org In-Reply-To: <87bscwe36t.fsf@tc-1-100.kawasaki.gol.ne.jp> X-Mailer: Evolution/1.0 (Preview Release) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:2439 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:2439 On Sat, 2002-04-06 at 19:56, Miles Bader wrote: > Colin Walters writes: > > In the interim, I will change ibuffer to use overlays for some > > properties. But for what it's worth, I think we should move towards an > > XEmacs-style "extent" mechanism. > > I thought `extent's were more like overlays, except optionally > persistent. No? Ok, I looked at the XEmacs manual a bit, and yes, that appears to be the case. Note that they have built a text properties/overlays type API on top of their extent mechanism. > In any case, perhaps you're right that text-properties should be > optionally buffer-specific, but that doesn't mean it's the proper thing > to get rid of the distinction between text-properties and overlays. > > Overlays are distinct _objects_ that can be manipulated as such, and > lend their properties to the underlying buffer they're in, whereas > text-properties are not independent of the text at all. > > These very different interfaces are both useful in different circumstances. That's what I thought at first, too...but I've personally *never* encountered a situation in which I've wanted to use the overlay API.