From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Question about copy-region-as-kill Date: 10 Apr 2002 18:27:34 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: <5x3cy3semh.fsf@kfs2.cua.dk> References: <87ofh09xjq.fsf@alice.dynodns.net> <200204050602.g3562Dl18586@aztec.santafe.edu> <87bscx7rlf.fsf@alice.dynodns.net> <3791-Sat06Apr2002101927+0300-eliz@is.elta.co.il> <873cy9nsom.fsf@alice.dynodns.net> <87wuvk77mc.fsf@wesley.springies.com> <200204081553.g38FrFM10159@rum.cs.yale.edu> <87zo0dc2em.fsf@alice.dynodns.net> <5x3cy5md5e.fsf@kfs2.cua.dk> <200204101424.g3AEO8N20963@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1018452472 32204 127.0.0.1 (10 Apr 2002 15:27:52 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 10 Apr 2002 15:27:52 +0000 (UTC) Cc: johnw@gnu.org, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16vK0m-0008NJ-00 for ; Wed, 10 Apr 2002 17:27:52 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 16vKG6-0004pQ-00 for ; Wed, 10 Apr 2002 17:43:42 +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 16vK09-0002OZ-00; Wed, 10 Apr 2002 11:27:13 -0400 Original-Received: from mail.filanet.dk ([195.215.206.179]) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 16vJzq-0002NZ-00; Wed, 10 Apr 2002 11:26:54 -0400 Original-Received: from kfs2.cua.dk.cua.dk (kfs2.local.filanet.dk [192.168.1.182]) by mail.filanet.dk (Postfix) with SMTP id 250017C047; Wed, 10 Apr 2002 15:26:41 +0000 (GMT) Original-To: rms@gnu.org In-Reply-To: <200204101424.g3AEO8N20963@aztec.santafe.edu> Original-Lines: 55 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:2508 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:2508 Richard Stallman writes: > It might be possible to divide all major modes into a few named > categories, such that we could design a reasonable plan for what to do > with text props on copying of text, given the category of the buffer > being copied from and the category of the buffer being copied to. This scheme may cover perhaps 90% of all cases, so I still think having buffer-local lists of properties to discard on copy/yank would provide a (possible) solution for the last 10%... > > Here is a starting list of categories: > > A. Buffers where properties are determined from the characters. > (E.g., programming language mode using font-lock, Rmail, and Info.) > > B. Buffers where properties are put on by Lisp code but can't be > determined from the characters. (E.g., the minibuffer, the output > of list-faces-display, and Shell mode). > > C. Buffers which should have no text properties. > (E.g., programming language mode without font-lock). > > D. Buffers where properties can be assigned by users. > (E.g., Enriched mode, and maybe Fundamental mode). > > Perhaps all text properties should be discarded when copying into > buffers of categories A, B and C. But what should be done with images > copied into these buffers? Again, it depends... E.g. if we enhance RMAIL to show small icons for unread or urgent messages (or whatever), we don't want to copy those images -- but if a mail message contains an image, we would (probably) want to copy that (as an image). > > Perhaps certain specific properties should be discarded when > copying into category D buffers. > Such as mouse-face and read-only... > Are any more alternative categories or subdivisions of them needed? Can't think of any, but I suppose there will be those 10% of special cases which will never fit (entirely) into a specific category. But what about (also) having a user command: yank-without-properties which can be bound to C-Y (when supported) and C-x C-y? -- Kim F. Storm http://www.cua.dk