From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sat, 01 Oct 2022 12:53:18 +0300 Message-ID: <83sfk7c1kh.fsf@gnu.org> References: <83pmfdduix.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38734"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 01 11:54:39 2022 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 1oeZCh-0009tL-I2 for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Oct 2022 11:54:39 +0200 Original-Received: from localhost ([::1]:54760 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oeZCg-0006ve-9G for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Oct 2022 05:54:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38068) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeZBc-0006F4-W6 for emacs-devel@gnu.org; Sat, 01 Oct 2022 05:53:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59422) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeZBc-00071b-Bf for emacs-devel@gnu.org; Sat, 01 Oct 2022 05:53:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=dgYpflUZSBoGBtajekCdPOMiW74OF29xdEwak0Bt7KA=; b=LhYeXZPtD4qI JISIJA3mLVB8avDwL0XlzoM2Gs4gJRrbxhAeEGm84ySM8En31YTKmG8m3y0hBv2fM8tRG5WnwXI2g 6j87EVRCjIYdbi5TJQvt4cf9c33beAGkDRSzgSmFwLbF7aI+HqJTm3F0hBr4acOwjH8MVtvR2Bz3s Zm4D9Gh6icBqk18LzKblOe4Z1G0xKX7mPLyFIRm9Rb61CLc6w1qJ3BWJVwoE0JKF9USPg9zRfV8dO nxaro1nYQktdL2nmgVvpkM9YQHK7jMBvQjfUAE/cGbd+dZc6OBzvLCTuWauvGQljvfMbNWRxZiGGH SMAjt03ELPle2GUatR/ljw==; Original-Received: from [87.69.77.57] (port=1563 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeZBb-0007xk-BK; Sat, 01 Oct 2022 05:53:31 -0400 In-Reply-To: (message from Richard Stallman on Sat, 01 Oct 2022 05:28:53 -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" Xref: news.gmane.io gmane.emacs.devel:296545 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Sat, 01 Oct 2022 05:28:53 -0400 > > > Sorry, no. We will not start a dispute about renaming eglot, because > > that would delay its merge, and we don't have time for that luxury. > > We want eglot to be part of Emacs 29. > > We can make this decision in a week. That's not possible, not with these decisions. And even a week's delay is too much. > > As for more basic arguments why not rename it: this package is not a > > new one, it is used by many people as a 3rd-party package. > > We can keep `eglot' as an alias for years or decades, or forever, > if we choose a helpful name as the principal one. > > If there is no workable way to define alias names for packages, we > should create one now. That again is not something to consider so close to cutting the release branch. We have enough to do with landing Eglot to keep us busy till then. > The crucial thing is to have the various names > in the _list of packages_, with the more helpful name preferred. One more package with a name that needs a description is not a catastrophe. We already have a few. Please help me get Emacs 29 on time and also with enough features to justify a major release. I _need_ that help, and I need the understanding to go with it. I do NOT need proposals that will make the job harder. Please bear with me.