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: HELP, PLEASE! Syntax problem! Date: Fri, 27 Nov 2009 10:56:34 +0100 Organization: Organization?!? Message-ID: <87d434qoj1.fsf@lola.goethe.zz> References: <20091125125810.GA4734@muc.de> <20091125203039.GA4874@muc.de> <20091125221328.GB4874@muc.de> <87hbsi87pw.fsf@uwakimon.sk.tsukuba.ac.jp> <20091126085334.GA2737@muc.de> <87einl2soe.fsf@uwakimon.sk.tsukuba.ac.jp> <20091127091607.GA3245@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1259315841 5987 80.91.229.12 (27 Nov 2009 09:57:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Nov 2009 09:57:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 27 10:57:15 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NDxZi-0003b0-5B for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2009 10:57:14 +0100 Original-Received: from localhost ([127.0.0.1]:59389 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDxZh-0001E5-LN for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2009 04:57:13 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDxZZ-0001DX-Ot for emacs-devel@gnu.org; Fri, 27 Nov 2009 04:57:05 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDxZV-0001Cy-Qy for emacs-devel@gnu.org; Fri, 27 Nov 2009 04:57:05 -0500 Original-Received: from [199.232.76.173] (port=59867 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDxZV-0001Cv-Gj for emacs-devel@gnu.org; Fri, 27 Nov 2009 04:57:01 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:40704) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NDxZU-0008Gw-NR for emacs-devel@gnu.org; Fri, 27 Nov 2009 04:57:01 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NDxZT-0003V9-3Z for emacs-devel@gnu.org; Fri, 27 Nov 2009 10:56:59 +0100 Original-Received: from p5b2c260c.dip.t-dialin.net ([91.44.38.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Nov 2009 10:56:59 +0100 Original-Received: from dak by p5b2c260c.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Nov 2009 10:56:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 59 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c260c.dip.t-dialin.net 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/23.1.50 (gnu/linux) Cancel-Lock: sha1:GnHAnoM1wT5p1fFVlM88UpzLUOI= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:117862 Archived-At: Alan Mackenzie writes: > On Fri, Nov 27, 2009 at 12:48:33AM +0900, Stephen J. Turnbull wrote: >> Alan Mackenzie writes: > >> > Just as a matter of interest (ha!) Stephen, does XEmacs have an >> > equivalent to the 'category text property? > >> No. > > That's a shame. > >> I'm not sure how much farther you can push that kind of thing, but >> clearly it works for you now. > > Well, for one thing, rather than just having the 'category property, > you could allow any property to be made "categorical". Then you could > introduce all sorts of rules as to which "categorical" property > prevails when several have conflicting settings of a particular > property. ... ;-) > > But, as RMS would undoubtedly say, there doesn't seem to be any need > for such an "advanced" feature. > >> Eventually I guess we'll have to match the Emacs API, but we don't have >> it now. > > It's more than an API: it's a fundamental feature. Without it, the > only way to change a text property on ALL characters of some class is > to scan through the buffer, which would be unacceptably slow for what > I need to do. > > So, yes, please feel free to get it implemented in XEmacs! You are underestimating XEmacs. It has a function iterating over all extents (their equivalent of both overlays and text properties) in a half-/open/closed range that have a particular set or state of properties. So you can say something like "give me all extents for which the property 'category happens to be 'text". Something like (map-extents (lambda (extent) ...) some-flag (point-min) (point-max) another-flag and-yet-another 'category 'text) You'll be brooding two hours over the documentation of this function, experiment another half an hour, and you are there. XEmacs calls something "API" comparable to a mathematician calling a proof "trivial". Mostly synonymous with "possible". Just because XEmacs has a single concept and a single work function for something does not mean that it can't be made to do a hundred things. You'll be muttering bad things through your teeth whenever you are reduced to reverting to map-extents. But it is there. And it does almost any job. -- David Kastrup