From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Lift {global,local}-key-binding to Lisp Date: Fri, 15 Jan 2021 05:16:20 +0100 Message-ID: <87o8hqhm23.fsf@telefonica.net> References: <83zh1cbpua.fsf@gnu.org> <83lfcvb7pj.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="24083"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:7HH+m6Ep6oiyJzOjsbfknx7TQe0= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 15 05:17:56 2021 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 1l0GYe-0006C0-8O for ged-emacs-devel@m.gmane-mx.org; Fri, 15 Jan 2021 05:17:56 +0100 Original-Received: from localhost ([::1]:42220 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l0GYd-0004kM-4a for ged-emacs-devel@m.gmane-mx.org; Thu, 14 Jan 2021 23:17:55 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57582) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l0GXK-0004J7-7E for emacs-devel@gnu.org; Thu, 14 Jan 2021 23:16:34 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:41552) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l0GXI-000545-Es for emacs-devel@gnu.org; Thu, 14 Jan 2021 23:16:33 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1l0GXB-0004Yd-FX for emacs-devel@gnu.org; Fri, 15 Jan 2021 05:16:25 +0100 X-Injected-Via-Gmane: http://gmane.org/ 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.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:263062 Archived-At: Eli Zaretskii writes: >> Emacs will be around in 40-50 years still, and we should maintain it >> with that in mind. Every time we make code more readable and >> maintainable, we make our life easier in the long run. > > I don't really see how moving stuff to Lisp in these cases makes the > code more readable or maintainable. You basically wrote the same code > in Lisp as it was in C. > >> Of course, any such change taken in isolation will look like something >> we could also live without, but many such incremental improvements over >> time will start to make a difference for the better. Clean and >> maintainable code is a good thing, and Lisp is better for that than C. > > I disagree, so let's please not do that unless we also add some > significant improvements or simplification. Along the years you repeatedly and justly expressed concerns about the future maintenance of the C code base due to lack of hackers with the required skills. Anything that reduces the number of lines of C will mitigate that concern. Plus, moving things to Elisp will remove the requirement of knowing C (and all its Emacs-specifc idioms) for hacking on the corresponding features. I look forward to the time when, thanks to native-comp and FFI, everything is implemented on Elisp except for a tiny C core. Looking at the Emacs C source code it is clear that it was written with an "i-would-rather-be-doing-this-on-Lisp" mindset. Let's go for the real thing.