From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Fri, 30 Sep 2022 10:59:26 +0200 Message-ID: <87tu4pb5ld.fsf@thornhill.no> References: <87edvtxo5k.fsf@posteo.net> 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="623"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= To: Philip Kaludercic , Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 30 11:09:30 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 1oeC1M-000AM4-TY for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Sep 2022 11:09:25 +0200 Original-Received: from localhost ([::1]:39370 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oeC1L-0003FK-W6 for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Sep 2022 05:09:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57354) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeBrw-0002qI-VR for emacs-devel@gnu.org; Fri, 30 Sep 2022 04:59:41 -0400 Original-Received: from out1.migadu.com ([2001:41d0:2:863f::]:13577) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oeBrt-0001pb-Fe for emacs-devel@gnu.org; Fri, 30 Sep 2022 04:59:40 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1664528369; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cR8MctWN3GwYPHHiwST/LyBAPpzbam19rsQVtqDOXpk=; b=aBb3c6bpZiXDpQ3XzmChBV+gfdRl13v7INQwM84Odk7D5ou8Rx6wEE0Wewrh5ETx25AtPq pDWjwHAK1vgOiRavp4VUBZUQDe/djNZ0JcqwXHkv0DPiyyuKE7qRNaQf9Qsr9osjE5mlRF S9zg8fse+TMuEKPshMcQaFxekt2Z+eNyvdq7OToZv2w1+H8sLmhUdzIZ7h2Z/mgv2HRe50 77T9YspYZfA/aF7220ZQMvgH+IhBGlpEKzNS2OQllDNnbAztAoxRYj0XRXqk7SxrNl4VF8 w8+TExfmG57vJhyv+K/y9lVzdYbDLStgG/5MWgB5BKL9l2HZ4fLXr+ENXC3bMw== In-Reply-To: <87edvtxo5k.fsf@posteo.net> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:2:863f::; envelope-from=theo@thornhill.no; helo=out1.migadu.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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:296498 Archived-At: Philip Kaludercic writes: > Stefan Kangas writes: > >> Hi all, Jo=C3=A3o, >> >> Now that we're getting closer to merging eglot, I think it is our last >> chance to (re-)consider that "eglot" is not the ideal name. It has some >> charm, of course, but it is quite non-descriptive and it's hard (read: >> impossible) to understand what it does based on the name alone.[1] > > I can only agree. Especially because there are a number of packages > starting with "el...", which makes misreading the package name as > "elgot" very easy (which is still how I pronounce the package when > speaking to this day). > >> As for names, lsp-mode would be the obvious choice, but some other >> package has occupied that prefix (too bad). I therefore propose >> renaming it to elsp-mode and using the elsp-* prefix for it. >> I like elsp, so much so that my play-fork of eglot is named exactly that[0].=20 >> At the very least, we should consider adding some alias, like >> `start-lsp', and/or `lsp-start'.[2] > > I think that even using the word "lsp" suffers from the same issue, as a > lot of people still have no idea what LSP is (even if they are using > it). I don't have a better suggestion but maybe mentioning the word > "intelligence" or "ide" would be better. > I think referring to it as an integration with lsp by its name should be just fine. It is exactly that, and why not refer to it like the rest of the ecosystem? As a tangent I remember the discussions we had here on tree-sitter, and whether it should be called ts, treesit, tree-sitter etc. I don't understand why referring to it by what it actually is is a problem. In this case, elsp, or elsp-mode seems like the obvious choice, considering that the better name already is taken. In addition, neither LSP or tree-sitter looks like tech that will vanish the next week, so relying on users learning what it is in time should be fine, IMO. Theo [0]: https://git.sr.ht/~theo/elsp