From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Emacs as word processor Date: Tue, 26 Nov 2013 16:05:01 +0900 Message-ID: <878uwbej8i.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87vbzqfgd6.fsf@uwakimon.sk.tsukuba.ac.jp> <83vbzkcx20.fsf@gnu.org> <83d2lrczi7.fsf@gnu.org> <8338mmcsd9.fsf@gnu.org> <83txf1blf2.fsf@gnu.org> <87txf133yd.fsf@zigzag.favinet> <83r4a5bj5x.fsf@gnu.org> <87mwktdy6r.fsf@uwakimon.sk.tsukuba.ac.jp> <83iovhb0ez.fsf@gnu.org> <87k3fxdpmg.fsf@uwakimon.sk.tsukuba.ac.jp> <837gbwbcsx.fsf@gnu.org> <87d2lnevq7.fsf@uwakimon.sk.tsukuba.ac.jp> <83y54bak6p.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1385449532 24410 80.91.229.3 (26 Nov 2013 07:05:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 Nov 2013 07:05:32 +0000 (UTC) Cc: ttn@gnuvola.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 26 08:05:37 2013 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 1VlCiG-0008P3-Nd for ged-emacs-devel@m.gmane.org; Tue, 26 Nov 2013 08:05:36 +0100 Original-Received: from localhost ([::1]:56791 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlCiG-000120-6x for ged-emacs-devel@m.gmane.org; Tue, 26 Nov 2013 02:05:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47787) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlCi4-00011o-TO for emacs-devel@gnu.org; Tue, 26 Nov 2013 02:05:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlChx-0000PR-86 for emacs-devel@gnu.org; Tue, 26 Nov 2013 02:05:24 -0500 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:44870) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlChp-0000Aq-Ac; Tue, 26 Nov 2013 02:05:09 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 8657F970A22; Tue, 26 Nov 2013 16:05:01 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 787E41A5193; Tue, 26 Nov 2013 16:05:01 +0900 (JST) In-Reply-To: <83y54bak6p.fsf@gnu.org> X-Mailer: VM undefined under 21.5 (beta34) "kale" 182d01410b8d XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 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:165744 Archived-At: Eli Zaretskii writes: > > Of course you can write code that discards those properties, but > > really, that's not what you want. Some properties should never be > > copied (and for the exceptions, it's not that burdensome to query and > > reapply those properties). That should be an attribute of the > > property itself, not the code that copies or moves text. > > We have yank-excluded-properties for that. Yeah, but it currently contains only one presentation property (invisible) by default. Things like a particular font or color used for emphasis are likely to be incorrect in a different document, and occasionally even when moved to a different context in the *same* document. Indentation, enumeration, marginal annotations similarly. My point is that dealing with these cases is going to require attention to a lot of fine detail, and the text-property API is much coarser than that. Of course you could proliferate properties ("non-copyable-face"), and add code to deal with them. But having an additional level of indirection (which is being called "style" in this thread) is going to be very useful in organizing these things.