From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sat, 01 Oct 2022 05:28:53 -0400 Message-ID: References: <83pmfdduix.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5751"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 01 11:30:33 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 1oeYpN-0001Gr-1G for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Oct 2022 11:30:33 +0200 Original-Received: from localhost ([::1]:49560 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oeYpL-0003Z8-DS for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Oct 2022 05:30:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56014) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeYnl-0002Vp-Se for emacs-devel@gnu.org; Sat, 01 Oct 2022 05:28:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51376) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeYnl-0003pb-L7 for emacs-devel@gnu.org; Sat, 01 Oct 2022 05:28:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=JwcVczdcZiePj5rIVYcumRtwo+g5earMNKPJawy+2Ac=; b=R5pG6hdQiQYo N8yK/qzcwqLtcspWaICXbuT4w7E5DfkVdnt4XO1mhFIFCoj/PJlUnilYdCXVsBTpLuwXwvuVWD/S/ RkaqlpCsb3jsGNcnA/zWls/CQlIgVJrOM3EulT08d5qk0EPmAnbL55Sj/ut/gWNlUYMLdxYvsvFld htbrFTTXieRM9KDWNMAnYojT6mhfvwE3QA6Jho8zkEWHKzZnHjRKSw2TJ46aXlknMHL1Tc+0mAOll auLdRcP0H2pUlvPN/Z58Y4gyhuUtwuutRoIv7e12Se1TUrPPGcwo6tkjTnzvBjgHUsH8lKStvIevL aRBOD+jsk9ZSh9KxaxiCYQ==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1oeYnl-0006WJ-2X; Sat, 01 Oct 2022 05:28:53 -0400 In-Reply-To: <83pmfdduix.fsf@gnu.org> (message from Eli Zaretskii on Fri, 30 Sep 2022 13:30:14 +0300) 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:296544 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > 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. Now, before including a package in Emacs, is the last good time to choose a helpful name. The policy that "We have left the issue so long that it is too late to choose a better name" leads predictably to accumulation of unhelpful names. I speculate that this has been at work for decades, resulting in so many unhelpful package names now in Emacs. > 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. The crucial thing is to have the various names in the _list of packages_, with the more helpful name preferred. The names of the package's entry points are less crucial. We know how to give them aliases, but if they are numerous, that would be more nuisance than it's worth. How many entry points does this package actually have? Given the existence of multiple packages for dealing with language servers, calling one of them just "language server" or "lsp" seems bad. Rather, helpful names will show people (1) what job all these packages do and (2) that they are different ways to do it. Ideally, also, also what is special about each of these packags, if we can come up with good ways to do that. It may not be practical. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)