From xemacs-m  Sat Aug 23 02:39:18 1997
Received: from firewall1.Lehman.COM (firewall.Lehman.COM [192.147.65.66])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id CAA18960
	for <xemacs-beta@xemacs.org>; Sat, 23 Aug 1997 02:39:18 -0500 (CDT)
Received: from relay.messaging-svcs2.lehman.com by firewall1.Lehman.COM (8.8.6/8.6.12) id DAA07429; Sat, 23 Aug 1997 03:37:15 -0400 (EDT)
Received: from cfdevx1.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id DAA12971; Sat, 23 Aug 1997 03:36:43 -0400 (EDT)
Received: from localhost by cfdevx1.lehman.com (4.1/Lehman Bros. V1.6)
	id AA08426; Sat, 23 Aug 97 03:36:10 EDT
Message-Id: <9708230736.AA08426@cfdevx1.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Face: #<@""pDMxa>Mr$Wp[^l7e1RwB6]&7pRp,f=|)6y5?t45X$y(xx.x^?k~;-d>s:SL86Qt82U
 'M!RC3LrDvD/LjiYdGO!:\/\qx?YabgGC9%xw5%0-W05LRvyu9vB9TYk%5PN|C*0WgrXD-L0'g3j;h
X-Windows: The art of incompetence.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: [bug] add-text-properties 
In-Reply-To: Your message of "Wed, 20 Aug 1997 17:55:40 EDT."
             <QQddlv26398.199708202155@crystal.WonderWorks.COM> 
Date: Sat, 23 Aug 1997 03:36:01 -0400
Sender: rickc@lehman.com

    Date: Wed, 20 Aug 1997 17:55:40 -0400 (EDT)
    From: Kyle Jones <kyle_jones@wonderworks.com>
    
    Colin Rafferty writes:
     > The real question is, why does `kill-new' (low-level) copy any
     > text properties at all?  I cannot think of one example where I
     > would want the text-properties to be copied.
     > 
     > But maybe this is because I never did any property hacking in emacs.
    
    If you don't want the properties to be copied with the text, you
    should use raw extents.  Why call them 'text properties' if they
    don't fall the text when you copy/move it?

Is there a way for me to force an arbitrary package to use extents in
favor favor of properties?

A typical example for me is that I grab some piece of a buffer
generated by some package, e. g. a GNUS article buffer or a w3 page,
and yank it somewhere else.  In every case that I can recall where
yanked text carried colors along with it, it was not what I wanted.

While I'm sure that there's a better way, I've found myself tossing
the text in a temporary file, deleting the buffer and then doing a
find-file, in order to strip off the excess baggage.  Blech...

I liked the suggestion to have a default set of kill-ring-related
bindings that operate on pure text -- the kind of stuff that gets
written out to a file -- and an alternate set that grabs the other
stuff.

Could one of the proponents of property copying give some examples of
situations where most people would want/expect properties to be copied
while doing manual cut-and-paste operations?

			Rick

