From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: buffer segments, uniform and automatic (was: Re: [Elisp: 8 out of 10 problems] I think the last one! (point)) Date: Tue, 13 Aug 2024 15:13:01 +0200 Message-ID: <87jzgkftwi.fsf_-_@dataswamp.org> References: <875xs7zzik.fsf@dataswamp.org> <87ikw7xnji.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10990"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:FyHMv24yYeC/nAdp1exeIykEXv8= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 13 15:25:25 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sdrWf-0002iF-HZ for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Aug 2024 15:25:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sdrVo-0005GI-JI; Tue, 13 Aug 2024 09:24:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sdrKt-0005Ed-Rg for emacs-devel@gnu.org; Tue, 13 Aug 2024 09:13:15 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sdrKs-0001PO-3d for emacs-devel@gnu.org; Tue, 13 Aug 2024 09:13:15 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1sdrKm-0000wN-LN for emacs-devel@gnu.org; Tue, 13 Aug 2024 15:13:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 13 Aug 2024 09:24:30 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322707 Archived-At: > Okay, I can make out 'begin' and 'length'. Without looking, > I do not understand at all what 'reg' is supposed to mean. > region? regexp? register? I came up with an idea how to do this! It is based on this policy: 1. Everything has a beginning and an end. 2. Everything belongs to something else. 3. The only standard worth its name isn't the one that comes from ISO, or the one in a manual, it isn't even the one the best programmers (almost) always stick to - it is the one created by a computer program. So as for the segments in a text mode buffer, as for point (2), it would look something like: [ buffer [ paragraphs [ sentences [words] ] ] ] Definitions of each has to be setup manually and individually, as for (1), so for example for word it could be (list (progn (forward-word) (forward-word -1) (point)) (progn (forward-word) (point))) Then the program will define a set of functions for each segment type, the same for each. Note that so many common operations can be defined from the definition, i.e. the (BEG END) pair: -len is (- END BEG) -reg is (BEG END) -beg is BEG -end is END -cur is (buffer-substring-no-properties BEG END) ... Everything else is then based on combinations of those: -prev of -beg and -cur -next of -end and -cur ... And it goes on: -all of -cur and -next (for some outer BEG END) -count of `length' and -all (for some outer BEG and END) I'm working on it now! PS. Change of subject line as I think the previous one with [square brackets] hindered the thread from being archived online. -- underground experts united https://dataswamp.org/~incal