From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sun, 09 Oct 2022 07:57:18 +0300 Message-ID: <83fsfxk30x.fsf@gnu.org> References: <83pmfdduix.fsf@gnu.org> <86wn9ji3ma.fsf@gmail.com> <86tu4lsnqk.fsf@gmail.com> <8335c0p2fn.fsf@gnu.org> <83leproov6.fsf@gnu.org> <83fsfzonwn.fsf@gnu.org> <5a1e604c-4500-a476-da3d-259d9057a7f0@yandex.ru> <838rlromxu.fsf@gnu.org> <83h70dk3wf.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10403"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 09 06:58: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 1ohOOU-0002Z0-Jq for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 06:58:30 +0200 Original-Received: from localhost ([::1]:48216 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ohOOT-0007Ch-Ab for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 00:58:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37696) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohONI-0006Lv-9G for emacs-devel@gnu.org; Sun, 09 Oct 2022 00:57:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34680) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohONI-0005Ob-1j for emacs-devel@gnu.org; Sun, 09 Oct 2022 00:57:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=8HNiJozxMDqX1CSYa4JYwzpRyEjatZrVSwTOwu0VUZI=; b=Eq9Qjk5csgeU sLX/NcGCMc+scCfaEtNmk9QqmlqXJNY4nhSLlRHOu+Z6uiMDj2Q2x58Jo0z30qR9BwoUYhrqJFOAC wrKlEtvZqREjXYwpRg8+ZLXMznGXT+5NlUfFnDcx6rHCJYuDFlt4aEWfRc6bQWV3d+ogb/BcDJS/p q8duL2PLndrlKe2ejw3LWo3j5hfOiVuJlIgiy5A7NBLKxHmHdSIHEMGBgOPalfcV8YCExx0hDFrOS xJCiMzEbaMaL/FhctHBiLscajmZJfTyZFkM2J7JLZMa4d2UJXz/oeOCJuN9/9AlUVmi0vH9rvkHRk X1UsH5zEgbvqBOb3JoEyaQ==; Original-Received: from [87.69.77.57] (port=3833 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohONG-0000Dm-TA; Sun, 09 Oct 2022 00:57:15 -0400 In-Reply-To: <83h70dk3wf.fsf@gnu.org> (message from Eli Zaretskii on Sun, 09 Oct 2022 07:38:24 +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:297243 Archived-At: > Date: Sun, 09 Oct 2022 07:38:24 +0300 > From: Eli Zaretskii > Cc: emacs-devel@gnu.org > > > From: Richard Stallman > > Cc: emacs-devel@gnu.org > > Date: Sat, 08 Oct 2022 18:34:03 -0400 > > > > > Yes, so take python-mode as an example. It has both tree-sitter > > > support and Eglot support. How to use both? does it even make sense? > > > > Do they do the same jobs? Are they intersubstitutable, in principle? > > Not clear yet (to me). Dmitry says they are basically orthogonal in > the features they support. > > One difficulty here is that Eglot exists for some years, so what it > does and how is pretty clear; by contrast, tree-sitter support in > Emacs is very young, and where it could potentially develop needs more > study, at least on my part. For example, at least up-front, it sounds like the LSP specification supports both fontifications and indentation. Eglot, AFAICT, allows to request the language server to do the latter (via the eglot-format command), but doesn't support requesting information about token types, which could be used for fontification. So, at least in principle, the functionalities based on these two could overlap. If that is indeed so, we'd need to decide whether we support the overlapping functionalities or use each one of these packages for capabilities that are disjoint, whereby each functionality is supported by the package that does it best (for some value of "best").