From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Re Re: Renaming eglot -- or at least add an alias? Date: Thu, 6 Oct 2022 14:14:09 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14643"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.7+37 (a90f69b) (2022-09-02) Cc: emacs-devel To: Pedro Andres Aranda Gutierrez Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 06 13:33:16 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 1ogP7s-0003bt-Ex for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Oct 2022 13:33:16 +0200 Original-Received: from localhost ([::1]:49154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogP7r-0008V0-BI for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Oct 2022 07:33:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55084) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogOw7-00075J-UF for emacs-devel@gnu.org; Thu, 06 Oct 2022 07:21:07 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:55167) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogOw4-0006ej-5x for emacs-devel@gnu.org; Thu, 06 Oct 2022 07:21:07 -0400 Original-Received: from localhost ([::ffff:197.239.4.113]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 00000000000BA40E.00000000633EBA1E.000055B7; Thu, 06 Oct 2022 04:21:01 -0700 Mail-Followup-To: Pedro Andres Aranda Gutierrez , emacs-devel Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL=0.141, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no 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:297091 Archived-At: * Pedro Andres Aranda Gutierrez [2022-10-06 09:59]: > > On 5. Oct 2022, at 17:08, Alfred M. Szmidt wrote: > > > > It provides LSP client services to several Emacs features, yes. > > Having a client without this glue would be much less useful, because > > it would mean we'd need to develop that ourselves. > > would lsp-glue describe it better? lsp-client is meaningful as Eglot is already described as "A client for Language Server Protocol servers". In hacker's world inventing package names is not an easy task. Though it is important to understand that well named packages and functions contribute to popularity and usage in the world. See: https://github.com/joaotavora/eglot Myself personally, I did not find it appealing that I have to know various spell checking commands on the system, like ispell, aspell, but same is valid for many system commands, packages and similar. In general, we have to think that package names were historically limited in length and people had to be creative. Today, we don't have limited computers. My vision is that package names shall be totally descriptive. Their underlying files and file locations shall not and need not be visible to users. One shall be able to install packages in the manner that does not talk about their abbreviated names. What is package description it should be the package name. M-x package-install shall thus accept the description and not only shortcut or short and not understandable package name. cpio-mode? dismal? ebdb? evil? sesman? pyim? rubocop? eglot? I beg your pardon, but that is not human friendly. In my completion functions I am always using long descriptive names of elementary objects. Sometimes those objects can be of same name, in that case they are concatenated to their parents, groups, categories, for better distinction. And I use their ID numbers. The eglot entry in a completion function could look like: M-x package-install RET: A client for Language Server Protocol servers by João Távora [eglot]: That way user would get clarity what it is about. The abbreviated name may be parsed by function to understand which package to install. Multiple entries become possible: A client for Language Server Protocol servers by João Távora [eglot]: A client for Language Server Protocol servers by Joe Doe [lsp-client]: A client for Language Server Protocol servers by Minime [lsp-mode]: -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/