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: Re: 10 problems with Elisp, part 10 Date: Sat, 10 Aug 2024 00:39:50 +0200 Message-ID: <87ttft1ft5.fsf@dataswamp.org> References: <87sevj9b50.fsf@jeremybryant.net> <871q33rj7v.fsf@dataswamp.org> <86ed73qhly.fsf@gnu.org> <87frrjoryg.fsf_-_@dataswamp.org> <86wmkuq60j.fsf@gnu.org> <87a5hqq4v3.fsf@dataswamp.org> <87mslqes7m.fsf@web.de> <874j7ypvr4.fsf@dataswamp.org> <87mslqceby.fsf@web.de> <86bk25q33b.fsf@gnu.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="27736"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:STowZEoPn7Pc9BtMqE/hIycVIHQ= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 10 07:19:14 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 1sceVV-00076v-R6 for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Aug 2024 07:19:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sceVJ-0006ny-Gf; Sat, 10 Aug 2024 01:19:01 -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 1scYHD-0007ZA-P3 for emacs-devel@gnu.org; Fri, 09 Aug 2024 18:40:03 -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 1scYHB-0007dI-Qr for emacs-devel@gnu.org; Fri, 09 Aug 2024 18:40:03 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1scYHA-00018F-5n for emacs-devel@gnu.org; Sat, 10 Aug 2024 00:40:00 +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: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 10 Aug 2024 01:19:00 -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:322598 Archived-At: Richard Stallman wrote: > I dont know of an editor which doesn't have a concept of > buffers or the buffer. However, the GNU Emacs approach, > where you move poimt and then call fuctions which operate at > poit, is not the only possible way. [...] Well, okay, good effort obviously, and thanks for sharing the history as well. > When people criticize this functiob/command calling > convention, it is not clear to me what other alternative > they would prefer. Okay, sure! I would like something that is spacier, faster, easier to edit and read, with features to set it up completely. [ end :range 0< :default 73 :prefix-arg step :range-cut 2-10 :default 7 i :range 0<= :default 0 ] Even shorter: [ end :r 0< :d 73 :pa step :rc 2-10 :d 7 i :r 0<= :d 0 ] Also it would have: :prompt-string (:ps), :doc-string (:ds), and so on. Since people didn't like my use of the prefix-arg, one would have to have a :prefix-arg-policy as well then :) Anyway, not saying anyone should do it necessarily or anything like that, just saying that would be a fast, safe, easy-to-edit, and easy-to-read "interface interface" for the formal parameters, to me, it would be a pretty much optimal solution for the purpose. -- underground experts united https://dataswamp.org/~incal