From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: What's missing in ELisp that makes people want to use cl-lib? Date: Thu, 9 Nov 2023 12:34:09 +0000 Message-ID: References: <871qd8sfdx.fsf@posteo.net> <838r7g8pys.fsf@gnu.org> <87bkcbrgnr.fsf@posteo.net> <25924.21015.19614.951576@orion.rgrjr.com> <87bkc4jpja.fsf@dataswamp.org> <12da6bcb-1818-7fbe-12af-8d4607724332@gutov.dev> <83sf5fyx60.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38244"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, dmitry@gutov.dev, bjorn.bidar@thaodan.de, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 09 13:35:27 2023 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 1r14Fq-0009iM-RX for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Nov 2023 13:35:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r14Ey-0007TB-Gl; Thu, 09 Nov 2023 07:34:33 -0500 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 1r14Et-0007SB-3c for emacs-devel@gnu.org; Thu, 09 Nov 2023 07:34:28 -0500 Original-Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1r14Er-0001EK-2N; Thu, 09 Nov 2023 07:34:26 -0500 Original-Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2c50ec238aeso10426541fa.0; Thu, 09 Nov 2023 04:34:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699533262; x=1700138062; darn=gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=HQeDni8Mu7DKzeb+NSP+XqPcXXrkBUSFXfGHvHEPMC8=; b=FTV2srZTmOt/xSoCXxbouNeSFeuR0KXCXAvc+CsBRPT6tQpMHmstWtV8asqIont+GB YYNIDB0Z/yADaHJ9v2rBhFsvtBNk3PUYTqt+eXgXiOtJ3iid+mNtp9K9/SRnN2v0b7LS Yr0WR1dgL/Sb+hUO5hG4dI4kb2ce7CxRPYsuYP5JVkJ3IcWWhyLxAIMrTl9oQU7jMIWq dXF3BChGPQmOboxsIeEaYO9SHJLDAu6awM0cuZ1rCHjNdvLu96RyXvmstizmFG6qhVg3 ebZzH5B/7vVEWG2HdFUBhySlz0lMf/SYFGDWoYFgkAs+6BDSKgBlgaUKNCxZrfyxVusc Iq4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699533262; x=1700138062; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HQeDni8Mu7DKzeb+NSP+XqPcXXrkBUSFXfGHvHEPMC8=; b=V0oyYnAhZ2qgJ4e7nyryGTaVmwiaRerCS3YTcNPIVu2PobiDJq0aLivFcu54F0dhRp M72tEU7OhjPLEl3HobAcz63Ep32OayIxQnfLsx7/se6lstS+AktmUoszVmoUqrD0oNW9 cPGPVkN9e7gsrnSQnLmNBeOttJtm86l1z9UjpUuWoZTYJJ3wXZe8ilbf9KVxMR7L284D EfIoAr4yuj+7AxfaF6903OH0HIIOiE3neXSwNj4lFlJ+6u8noB2dye6eEsUOFmit4J5d VL72k2EjVl0Ajbejh/uf2fpmLjFSmYJgOx3nj2wgPt44EUIM7G9wqxWynpiFnoykpsqY Td2g== X-Gm-Message-State: AOJu0Yyv2cUeFlgaVMIo2nonPtvzpFLZeS8O1dURyQcMvwLaCaiXWy+v Z7HfiLP8zBseAxB8DDv1SC+f9djOcAqsjGDAGf4gwZw+5lBruw== X-Google-Smtp-Source: AGHT+IG5On9snX0lQ+PLceNI/VTGTDIRxORsWvNytBUJZH47Bxc3OHptr2SVmv2yulQYlpjRzIVngUJ2Yqgu9Ea1bio= X-Received: by 2002:ac2:4884:0:b0:507:a40e:d8bf with SMTP id x4-20020ac24884000000b00507a40ed8bfmr1255210lfc.7.1699533261694; Thu, 09 Nov 2023 04:34:21 -0800 (PST) In-Reply-To: <83sf5fyx60.fsf@gnu.org> Received-SPF: pass client-ip=2a00:1450:4864:20::22d; envelope-from=joaotavora@gmail.com; helo=mail-lj1-x22d.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:312403 Archived-At: On Thu, Nov 9, 2023 at 11:38=E2=80=AFAM Eli Zaretskii wrote: > > > From: Jo=C3=A3o T=C3=A1vora > > Date: Thu, 9 Nov 2023 11:06:02 +0000 > > Cc: Dmitry Gutov , > > Bj=C3=B6rn Bidar , > > emacs-devel > > > > So I propose we let programmers use their judgement. > > That's fair enough, provided that those same programmers step up to > become the Emacs maintainers, and thus share the burden to at least > some extent. Especially those of them who consider witty sarcasm a > useful style in a discussion like this one. Did you read the rest of the paragraph from which you extracted that one line? I'm advocating for being discriminate and Also, I would hope this is not a suggestion that I don't step to share the burden of maintaining things? I do, certainly for all the features that I have I added to core in the past 10 years and frequently also to parts of the code those features interact with. Do you often have to fix bugs in flymake.el, elec-pair.el, icomplete.el, eldoc.el, jsonrpc.el, etc... that I didn't care to take a look at in a reasonable time frame? More importantly, to what extent are you and others significantly or often hindered by the style I use there? I can't address what I don't know about. I can't track the bug tracker as closely as you do. If I'm missing or late about bug reports about such things, just ping me like you usually do. Or are you suggesting I should dumb down my style for when I'm dead and my code survives me? Just so you know, I think that's not entirely unreasonable. In fact if you read the pdf I linked to, it's a valid criteria for making decisions. But it's definitely not the only one. Who knows if Emacs 40's maintainer wouldn't have appreciated it if I had smartened it up even more and use _only_ cl-lib. Anyway, if there's some code of mine that's bothering you and you find inescrutable, point me to it and we can discuss it, of course. > The following is left as an exercise for the interested readers: take > a non-trivial piece of code that you never in your life have laid your > eyes upon, and decide what to do with a serious bug report about that > code, with or without a patch proposed by someone. A recent case in > point: bug#66970. Bonus points for doing this with code in a > programming language you don't command 110%, like C if you are mainly > a Lisp programmer or vice versa. Do you need help reading some Elisp construct or debugging? Is this meaningfully related to style in Lisp code? You want help reading hangul.el? (which doesn't seem to use cl-lib.el btw) Would you like help rewriting hangul-insert-character to support overwrite-mode, perhaps by leveraging post-self-insert-hook? I can help with that. If there is some deep required specific domain knowledge about input methods or how the Korean language works, you or someone else may have to help out with that. If C code is involved, it's not a problem. I'll have a better look later. The problem of maintaining other people's code (which btw is 95% of all my professional experience) is not about programming techniques or even languages at all, it's about domain knowledge. Jo=C3=A3o