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?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot Date: Sat, 22 Apr 2023 13:12:39 +0100 Message-ID: References: <87a5zj2vfo.fsf@gmail.com> <87a5z3izst.fsf@web.de> <83v8hr7qk9.fsf@gnu.org> <83pm7z7nkc.fsf@gnu.org> <4b63ef62-5e1c-3dcf-ec7b-06b69e79133b@gutov.dev> <83o7nj7mfn.fsf@gnu.org> <556e0fbb-215e-c11d-0e8b-73e97441abbb@gutov.dev> <83pm7y6fdo.fsf@gnu.org> <47140c27-ba63-ca7b-8b9e-cc38a6f9a866@gutov.dev> <838rem636a.fsf@gnu.org> <83leil4u63.fsf@gnu.org> <8a9d0e2b-6ae2-bcdc-efd0-52a44ac862bb@gutov.dev> <83h6t94hru.fsf@gnu.org> <7676c8d2-1324-31e7-38b3-de167ecf683a@gutov.dev> <624a26af-0c96-8d48-129f-79bc6a547ede@gutov.dev> 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="8223"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org, monnier@iro.umontreal.ca, Eli Zaretskii , larsi@gnus.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 22 14:13:16 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pqC7A-0001zR-OX for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 22 Apr 2023 14:13:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pqC6y-0001lw-LS; Sat, 22 Apr 2023 08:13:04 -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 1pqC6x-0001lH-69 for bug-gnu-emacs@gnu.org; Sat, 22 Apr 2023 08:13:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pqC6w-0002XK-T1 for bug-gnu-emacs@gnu.org; Sat, 22 Apr 2023 08:13:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pqC6w-0000Qt-AR for bug-gnu-emacs@gnu.org; Sat, 22 Apr 2023 08:13:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 22 Apr 2023 12:13:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62720 X-GNU-PR-Package: emacs Original-Received: via spool by 62720-submit@debbugs.gnu.org id=B62720.16821655791654 (code B ref 62720); Sat, 22 Apr 2023 12:13:02 +0000 Original-Received: (at 62720) by debbugs.gnu.org; 22 Apr 2023 12:12:59 +0000 Original-Received: from localhost ([127.0.0.1]:42046 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pqC6t-0000Qc-Cc for submit@debbugs.gnu.org; Sat, 22 Apr 2023 08:12:59 -0400 Original-Received: from mail-oi1-f180.google.com ([209.85.167.180]:60778) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pqC6q-0000QN-MQ for 62720@debbugs.gnu.org; Sat, 22 Apr 2023 08:12:58 -0400 Original-Received: by mail-oi1-f180.google.com with SMTP id 5614622812f47-38c35975545so2185115b6e.1 for <62720@debbugs.gnu.org>; Sat, 22 Apr 2023 05:12:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682165570; x=1684757570; 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=XeVTrKkeUf1o6ruG9AIo+Uon/7w98kCHvtXsgP2HOG0=; b=qJ88/ERiwCFC5CkIqGo8RICOeN13I74V+hqRW7qVBb1a/9xYqCdgS33YzFFiJwUZFq dypvkWecvYVYz/NJTliiUjNjU/2LpPzmlt7q/BKn0Bz1B/+Vv2mQq/rRMl891jKZ1CoR gKWqT7psrg7BdtyZ2Cu4wiRkJmGFLXeqcpxbITydvN0fsM85L6gCjAL6Jw2M0pfGrlfi 2EYrh4BKISLpWYeSMD1v7aXe+cU4Iaknd3gVf7v02Dvk+8U+JB3Tug/BXSttr7GqLKU6 ZAd0tgE16LROi8P+JgekLlTQyKBZANW0gQ5X271tRtkkKhgSnCO4pP6qSlV9lfVxYQjX 7gfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682165570; x=1684757570; 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=XeVTrKkeUf1o6ruG9AIo+Uon/7w98kCHvtXsgP2HOG0=; b=AJWOyHpDlCw+AZi5/SLjgRHIOXiGslSUL31o9nXIO8LbQNWO5xASNJhCUGLql53mPM llxAKtcpaPR/wwn/6H0oNYYDYlkTwZXpzaVy7b+fdZeYM5CPuifxAkPyBH98kZPfSvNP zwgVXjHpfToD7nz09VV8R6+Lrn4bEYxxDefYvLtoCxarNAGNlRvmKiS1TDtQyNzoxqEu wJoJKItNnbFQ8RzlIl07l+cs64UOmAVb8H9LoHsDchnOHkmMHneR+H7FLqBHydni8kPD 3RRqcoMLbPV7JW2z6mDvejEXDkKzEomdlekZlwtIGPp/kroohyjfe2m2nmzzKF57z3jk U+fw== X-Gm-Message-State: AAQBX9flFxnJm8UG8b58IlTgQf/QmKs2Uh3j+l3aNJSqsCeE0p/kJXZ2 8+0emK8Aa4oKSiDBp3dQSYJT5DdshP78rxDVTlk= X-Google-Smtp-Source: AKy350ZkDyE2nYS09ryh1E+XYvpU5aPndbu0I8NtF7tBth+f0cVPohn4WMi+U9VxSGWJd2cV4iTFbRzu6SQ2FGQOKpI= X-Received: by 2002:a05:6808:1383:b0:38b:4214:94f3 with SMTP id c3-20020a056808138300b0038b421494f3mr5414779oiw.24.1682165570616; Sat, 22 Apr 2023 05:12:50 -0700 (PDT) In-Reply-To: <624a26af-0c96-8d48-129f-79bc6a547ede@gutov.dev> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:260466 Archived-At: On Sat, Apr 22, 2023 at 12:39=E2=80=AFPM Dmitry Gutov wr= ote: > > But the difference from Emacs 28 is indeed unfortunate, no argument there= . > > Or if the new option stays around, I guess you could be recommending > they customize it first? No idea yet. I'm leaning eglot-update as it guaranteedly the most consistent. That or straight.el or elpaca.el. Or no recommendation whatsoever. I just got my first bug report about a user where I can't tell the version of Eglot being used but which is consistent with an older version being used, perhaps unknowingly. This is, of course, not unheard of, so let's see. > We might as well switch to the "update all the cores!" model later, but > hopefully by that time we have a good CI setup that tests the > compatibility of all core packages with all Emacs versions they are > supposed to support. Right, that makes sense. If it helps, Eglot's CI has been doing that for year now. It tests Eglot -- and its up-to-date dependencies -- in Emacs 26, 27 and 28. It's not very complex to set up. > Do you prefer that package-install-upgrade-built-in (together with the > behavior of package-install it enables) stays around? No, my opinion is that I find this user unfriendly, and of course even more so with the default value. I've already answered this early on in the thread. Creating customization points as a "cure" for haphazard design is not a good practice. It's like there are two package managers in Emacs. The package menu and the package-install. The "upgrade :core" cat has always been out of the bag in the first one fully, and in the second almost fully. And then there's the third "package manager", i.e. use-package's specific package-install behaviour. And nwo there is package-update which is almost a newborn, but is already inexplicably broken. Putting more customization variables into the mix is just adding variations to a very crowded field, more questions to ask, more fear-uncertainty-doubt. The "update all cores" is frankly the safest model IMO. Of course, I understand that others disagree -- and I even see their well. So knowing emacs-devel, I don't have any illusions. But I suspect they see this "update all cores" idea as some kind of gargantuan jump from what is in Emacs 28, when in reality it's not (again, because dependencies). And I also tend to think they disagree because they haven't been working with this and with users for as long as I have (and you have), so from afar it seems dangerous. Jo=C3=A3o