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 16:30:11 +0300 Message-ID: <834jwdjfa4.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> <83fsfxk30x.fsf@gnu.org> <87c5875e-e448-cd0f-942e-a1c8e3d57d22@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20900"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 09 15:31:14 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 1ohWOf-0005I6-NQ for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 15:31:13 +0200 Original-Received: from localhost ([::1]:49154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ohWOe-00084k-9c for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 09:31:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47990) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohWNb-0007Eb-WC for emacs-devel@gnu.org; Sun, 09 Oct 2022 09:30:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38436) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohWNb-00035t-M5; Sun, 09 Oct 2022 09:30:07 -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=JpSzCjuAvV2E0PVBJTUb3CZ1Elh2/iPT/NmJLCiR9c4=; b=LLrWotZO0FlE WVLGE8e+Q0V8EgtLgC2gElHKqmloEZl6jSfXfck0uHZyjV86C5YeIbbTrv+SU3xHu4+VcLbalYnbn GM6bPxYQoe78yZYK6jMSwrzgz3+IYdNde24RYwIZsntzJvVarpC8UWeu0q8IYVwbbISdhjAuL5PbV 2cc8UkI3Eg7Hs9hHlgQ3FIFjAs5BkPhmBYUiY3tUNbOyz3r0WAxxw+5vJNyRkl3JERic/c8uOTnB1 tG2Jqp1kXeHdEOwGmKX74tVf4jh4C1y+uUEflUdJrMhatyvDAplv6TpwklOpaDRGmJwVKaryf8qjK L401yRr1jmyZupppZ14tRg==; Original-Received: from [87.69.77.57] (port=4214 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 1ohWNa-0007yo-Ol; Sun, 09 Oct 2022 09:30:07 -0400 In-Reply-To: <87c5875e-e448-cd0f-942e-a1c8e3d57d22@yandex.ru> (message from Dmitry Gutov on Sun, 9 Oct 2022 15:44:19 +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:297262 Archived-At: > Date: Sun, 9 Oct 2022 15:44:19 +0300 > Cc: emacs-devel@gnu.org > From: Dmitry Gutov > > >> 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. > > LSP syntax highlighting is a new-ish thing, and apparently isn't > supported by Eglot. Further, passing the highlighting information over > the wire is bound to be slower than the in-process integration offered > by TreeSitter. > > Indentation - maybe, I'd have to check how well it works first. The > indentation code we have already seems to be good for the majority of > languages, and having it in Elisp makes it more easily hackable and > customizable. > > TreeSitter indentation logic will not be entirely in Elisp, but almost > as hackable nevertheless. > > > 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"). > > I'd recommend keeping the divide where I described it, but then keep an > eye out for whether one of the options makes a noticeably better job > somewhere at the other's turf. Maybe after Emacs 29. I'm not trying to make an argument, just point out that the jury is still out about these issues, and we need at some point make our minds.