From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Wed, 05 Oct 2022 09:01:25 +1100 Message-ID: <86pmf7utjp.fsf@gmail.com> References: <83pmfdduix.fsf@gnu.org> <86wn9ji3ma.fsf@gmail.com> <86tu4lsnqk.fsf@gmail.com> <83ill0vzit.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="11583"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.9.0; emacs 29.0.50 Cc: Eli Zaretskii , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 05 00:14:17 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 1ofqB7-0002rg-L1 for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Oct 2022 00:14:17 +0200 Original-Received: from localhost ([::1]:39794 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofqB6-0002Ti-EZ for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 18:14:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46664) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofq9z-0001T1-Vg for emacs-devel@gnu.org; Tue, 04 Oct 2022 18:13:08 -0400 Original-Received: from mail-pl1-x62f.google.com ([2607:f8b0:4864:20::62f]:45831) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ofq9y-0007bN-Ck; Tue, 04 Oct 2022 18:13:07 -0400 Original-Received: by mail-pl1-x62f.google.com with SMTP id u24so6853948plq.12; Tue, 04 Oct 2022 15:13:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:from:to:cc:subject:date; bh=vUCkoTmt55EtMqj/oEXOuATmOATV3aAEMYhLv3a5RXg=; b=qaQIf7rWA7Otc9tC9LQN21LQtYPcn60aYRjKSnYh0XhiZF9Lhf15LTT0T8eayQuoV5 BFoop3n0SybiQzDRIoxFimnIl2BRkt0LddynW9bCsrw50fyo3x99E1/TY2ff0dRH9koY Eei/1h5/wORYdO4V+qGLBAlmuKgKhEiS48e/ibl2rC1JJ6yWz0y7CR9G4LULbHj1qirj ZweUGkfx3U0mMLm1vJwCQ1NeO2Qvu/47mmK8hk4RMGUvFqmjtIoRK6lBZN36IPxfg0IA 9lKu+aWJTRyb1Q5Y6Y2y8I/9HAskcU3bEBRZIsz7rUl2JCqJ2JPGeXldDwO0jsdQi6lz +tuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:x-gm-message-state:from:to:cc:subject:date; bh=vUCkoTmt55EtMqj/oEXOuATmOATV3aAEMYhLv3a5RXg=; b=OFHEAPiD7nb4oamUqi+kjezQEN/0/tpivzxsqTYSOTWZtwpVrosMXXpmgDjQrQE/A6 e0Rz3eaxCQCHP7CQyhpBE9mr5yVlo3pwPLrLUkoxxAyHMP8VW1WPMuYKNdY9QSXvJe6F odPs3QIJPnHoSw7/8VSMO2mx1iTcdQPwd/PlOJBIMroavPxSuKgJCxkxey0wRKlX6DCo vbxjcVoIll1l2GGFA9q50AlK5ryxXna7b2hLzPWlGOS4qoDXyZAE8wWEhV1AfceHT5sk 7BZj/Px8ox5tiAPQ63Bb6zUq4mD4WZxybCVkfE7z4VgQclKTZLM5Y3raUyZ9z+wQZCfK 1WsA== X-Gm-Message-State: ACrzQf3UQjaDSLyzgmcTAOIL7tnUFLAMpI+PnHq7646u/ubxvCgzDdhv TUwDaRk2uo1cdfbvRHG96pyL3UuVTAA= X-Google-Smtp-Source: AMsMyM5bOKtf9t7yaNiehBM/eE56jFs/n1cOo3Kt7pb7kVSrmT/j/G4il0qSx3LRZlSvR8YWgFrY/g== X-Received: by 2002:a17:902:bb96:b0:17d:9ed7:e9af with SMTP id m22-20020a170902bb9600b0017d9ed7e9afmr17699068pls.15.1664921582283; Tue, 04 Oct 2022 15:13:02 -0700 (PDT) Original-Received: from dingbat (124-169-22-230.dyn.iinet.net.au. [124.169.22.230]) by smtp.gmail.com with ESMTPSA id t6-20020a1709027fc600b00179f370dbfasm9435639plb.26.2022.10.04.15.13.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Oct 2022 15:13:01 -0700 (PDT) In-reply-to: Received-SPF: pass client-ip=2607:f8b0:4864:20::62f; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x62f.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 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" Xref: news.gmane.io gmane.emacs.devel:296932 Archived-At: Richard Stallman writes: > [[[ 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. ]]] > > I think the clearest name for Eglot is Parse Code. > That's what all these enhancements have in common. > If you enable the Parse Code feature, various functionalities > will parse code (when possible, when supported, etc.). > > There's no need to eliminate the name Eglot. I think making Parse > Code an alias for it would do the really helpful job. Its source > files can be mostly unchanged -- but they should explain that the > package is also called Parse Code, and why. > > The main change is that Emacs should refer to the package and its > functionality primarily as Parse Code in menus and documentation. > That is how we will get the benefit of that name's clarity. A terrible name because it is misleading. Eglot does not do any code parsing. In fact, it knows nothing about the underlying code/language. As I've said MANY times in this thread, eglot is just a client which is the glue between Emacs and servers which implement the language server protocol. It is the servers that have all the language specific functionality. GO one step further. Consider a user who is having problems with the package they know as 'Parse Code". The first thing they will do is enter something in a search engine to try and find a result. The natural thing to do would be to include the package name in the search. Imagine all the 'noise' in the results if you search for 'Parse Code". Your answer will likely be "Ah, but we have kept the name eglot, so they can use that in the search!". So now what we have done is potentially create more confusion as we have a package known by two names and they need to know the original 'eglot' name in order to easily find relevant information. Let it go. You want a better name and none have been forthcoming. This is a non-issue and time to move on. .