From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yilkal Argaw Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sun, 2 Oct 2022 05:45:48 +0300 Message-ID: References: <83pmfdduix.fsf@gnu.org> <86sfk7hse3.fsf@gmail.com> 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="36990"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 02 04:47:00 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 1oep0N-0009R0-Jk for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 04:46:59 +0200 Original-Received: from localhost ([::1]:45408 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oep0L-0005Cf-Um for ged-emacs-devel@m.gmane-mx.org; Sat, 01 Oct 2022 22:46:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53168) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeozf-0004Uu-VL for emacs-devel@gnu.org; Sat, 01 Oct 2022 22:46:16 -0400 Original-Received: from mail-yw1-x1133.google.com ([2607:f8b0:4864:20::1133]:34686) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oeozT-0003RP-6I for emacs-devel@gnu.org; Sat, 01 Oct 2022 22:46:15 -0400 Original-Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-3573ed7cc15so34041487b3.1 for ; Sat, 01 Oct 2022 19:46:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date; bh=p6Ww9vgQiYNel4kkrI/kKPJRA9adg8+0iHv5P8djZDI=; b=kzxzJfPXZmKB3nG+e+N/yLGBGdD15UAfMSfMIkKUxr2ZHquRQqOiUoeeakuw7WKeak ovfCyCcVky9u5zS7lQNpJdhpDCYck+g3W9FRCcgyOj3ehPLSS9uMEmeEr6vjVn86Q49Y jzM62EZuMB99iBH8j3GutVThQCTpe+NGcqaHq4l1EhLjIi0EAmDulJ5Fd4Nwg8kTxW8V J0nbX0VdOGuWHNuhn/99BKgMgPcbIFTNjXrCZFEqXdzycef0Q8pk5AQroaWTzwo+Or4w xLGwcyCZS3xH6GScOLmRe+3+6zcEq2QQYfkD6gbfLWn/B2/nnJap/Vtz0JrZuYcIGASD KyGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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; bh=p6Ww9vgQiYNel4kkrI/kKPJRA9adg8+0iHv5P8djZDI=; b=PJlAWc84xebBxgFVfmr6F0ax3fR/c5Uv35UIuS67GHGuf28cfx5yeYxXLO/SyHT+ec 0wnTeOVRSAAXhujpWw0W3QhBhWplrBrnxWEyO7SYoZPsBLClagHZLNIrmzVI4rYv0YEq QKNKijSrvYMsAUvJR55pUwh+TKeqP/iloHS19DFRbalYVXc0+JPnmhmX7O8zP0TgfST2 kJWfEd5rITk9ZuKG5uqmjywUEQTRzY3j8Ggjvd/x7g6B6zJCQlu0hyGqTefUFZHfrL7V 9bcyRXZgA7qHe6w9b4vBop2BOgGqWRxsDjNzk4fwpFQFDbJHXnGlUjyRTkzmw9VVsb2I pf2A== X-Gm-Message-State: ACrzQf1DGHYHeOefMsGzsoTljWsUqR9nq1S7410FFJ3UEMfM6V11y1bQ aog7Ez1AZbPk/iyAe3kxULvCGsdTQpDETEhZ7Wg= X-Google-Smtp-Source: AMsMyM4lxH7nBLQirV8kELyfyrJH5+D9oKTP24JhXPnTR6DIfRJOkH3GEVZsXF8IhF2Nn0WLphTCxN1zg37BUZ7IS2s= X-Received: by 2002:a81:84c3:0:b0:355:1c82:19fc with SMTP id u186-20020a8184c3000000b003551c8219fcmr13725420ywf.269.1664678760345; Sat, 01 Oct 2022 19:46:00 -0700 (PDT) In-Reply-To: <86sfk7hse3.fsf@gmail.com> Received-SPF: pass client-ip=2607:f8b0:4864:20::1133; envelope-from=yilkalargawworkneh@gmail.com; helo=mail-yw1-x1133.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, 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:296570 Archived-At: > Personally, I would just stick with eglot as I think this whole argument > regarding the need for package names to describe their functionality is > misguided. Great if you can do it, but should not be a necessity. I agree. There is also the issue of the already established user base and documentation (including unofficial documentation that accumulated over the life cycle of the package by users documenting how they use it, how people should use, solutions to questions and issues etc). I don't think it is possible to backtrack and change them all to refer to a new name. =E2=80=9CWho knows a man's name, holds that man's life in his keeping=E2=80= =9D =E2=80=95 Ursula K. Le Guin, A Wizard of Earthsea with regards Yilkal A. On Sun, Oct 2, 2022 at 5:28 AM Tim Cross wrote: > > > Richard Stallman writes: > > > > > Can anyone suggest a way to describe the job that Eglot does, NOT > > using technical jargon, or implementation details such as "LSP"? > > Isn't that the crux of the issue - it seems nobody has any suggestion > any better than eglot. Quite a few of the suggestion are worse. > > One thing you could do is just call the package eglot-lsp, which might > give you the additional name info you seem to desire. The package > namespace could remain eglot-*, so perhaps would not have the overhead > and delay to release of Emacs 29 which a full rename would cause. > > Personally, I would just stick with eglot as I think this whole argument > regarding the need for package names to describe their functionality is > misguided. Great if you can do it, but should not be a necessity. > > In general, it seems only very simple and single purpose packages lend > themselves to clear descriptive names. For example, tempo, skeleton and > flycheck. Few packages which perform multiple functions seem to have the > sort of descriptive name you are after. The name closest to function I > can think of for eglot would be lsp-client, but that is too close to > lsp-mode and in general, too close to 'lisp' and 'elisp'. Using the full > name i.e. language-server-protocol-client is cumbersome, we be shortened > in actual use and will likely result in confusion with lsp-mode. > > A good name is the one which you can easily remember and > communicate. Once you are told what eglot does, you will remember > it. You don't need its function to be in the name. > > > Would the word "parse" be good? "Code-analyze"? > > I never used Eglot so I don't know what it does. > > No, none of those words/terms are appropriate. Eglot is essentially just > a client for servers which implement the language server protocol. It > simply takes the data provided by those servers and uses it to annotate > your code using flymake. It is just the glue between a language server > and flymake - we could call it language-glue or ide-glue! Neither are > jargon or too technical (I doubt IDE is considered jargon or technical > these days). > > If you are going to insist on a new name, I would suggest you also need > to understand what eglot is and what the language server protocol > architecture is about. Without these key elements, you are unlikely to > be in a position to judge the suitability of the name. > > See for example > > https://whatacold.io/blog/2022-01-22-emacs-eglot-lsp/ > https://langserver.org/ >