From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sun, 9 Oct 2022 15:44:19 +0300 Message-ID: <87c5875e-e448-cd0f-942e-a1c8e3d57d22@yandex.ru> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19336"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cc: emacs-devel@gnu.org To: Eli Zaretskii , rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 09 14:48:13 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 1ohVj3-0004nI-1r for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 14:48:13 +0200 Original-Received: from localhost ([::1]:34162 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ohVj1-000356-Ge for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 08:48:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49990) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohVfk-0000u1-Rp for emacs-devel@gnu.org; Sun, 09 Oct 2022 08:44:49 -0400 Original-Received: from mail-wm1-x335.google.com ([2a00:1450:4864:20::335]:39872) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ohVfi-0001Gn-PX; Sun, 09 Oct 2022 08:44:48 -0400 Original-Received: by mail-wm1-x335.google.com with SMTP id e10-20020a05600c4e4a00b003b4eff4ab2cso7041912wmq.4; Sun, 09 Oct 2022 05:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=m1eHzZ4IaC/0ALpcgcuxzsAa+VQdOFj1sWolW/b82Vs=; b=h6KDsTIRsBhguto/Sfvo+ZfZgABU85StQ0gnH0k68pRttuvQeP/+vsAjXBJq/iK3HD AZoWa8dOhv4gwK9K988h/pLN9D9Jc0mOXPCQG2GwAQRuTbeh7xNGxtNGQVQ04qlfrF4S y2BsMoB2u48eZCWAypz1+6BMxrbVRqNq4ctH9tgGLsfARWQXmujJIafYHGBTMoZezx1b 8IuGsq1dIqlzzGgSugkxmbMlIGZBxM9P+VtpLqwBaPK4NXVo2BWjQ5E2kvhTaFJBpbPp 9U/WQh6iYftdazsl5WumKC463J0oQbbYRp+4Hp5QnwTWQRk4RLLqSzJg6iYNIMiIdM4w idyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=m1eHzZ4IaC/0ALpcgcuxzsAa+VQdOFj1sWolW/b82Vs=; b=w4lRg/cvS0nQbnCwY4AOuvEx1kOPww2awSxH0WMgZoGVoymrHTgQjbOEzz5GWkrhg5 cHsbRZ6Q0EZ38GWENdM+HkzkJk+6qRDh12L7PW+JAZc+dT7KE6LdIsjwYi7/QFj036tU igZoTqJXFQooiTXaFuCq+1siiIGcIyr6hxPK+ffrv+F1HUUkkvA0B9nhe9mtvXh30aPZ Jf/U1JShJBF8xESBG1d4blkuBWqyXd2XgYw59xMTLrRpgNxsqx4NfOOnsEkmdwOKTOPp J4UzPaxfYwysynosZh48JwBCTHn0ANPj2xaeE6E3P9BiPPPKqe6nhdc5eL6ORwzuhmaf cneA== X-Gm-Message-State: ACrzQf3mnlnwv74Y43ZaO+HBY+W8xOLgiRTvu14ySxu59uidX+xcuxLi J6Afai73gtqd+DQ4O8Uu28REH91ilU4= X-Google-Smtp-Source: AMsMyM6yC7FNKRCYlgGebZVZPDYvxxclMP2NRPwJaDLUWUCTfdYzIU6DZgAjqKcWYT5KnjImKiu6CQ== X-Received: by 2002:a05:600c:35cf:b0:3b4:c0c2:d213 with SMTP id r15-20020a05600c35cf00b003b4c0c2d213mr17289303wmq.162.1665319461044; Sun, 09 Oct 2022 05:44:21 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id x11-20020a5d60cb000000b00228da845d4dsm6573338wrt.94.2022.10.09.05.44.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 09 Oct 2022 05:44:20 -0700 (PDT) Content-Language: en-US In-Reply-To: <83fsfxk30x.fsf@gnu.org> Received-SPF: pass client-ip=2a00:1450:4864:20::335; envelope-from=raaahh@gmail.com; helo=mail-wm1-x335.google.com X-Spam_score_int: -53 X-Spam_score: -5.4 X-Spam_bar: ----- X-Spam_report: (-5.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-3.934, RCVD_IN_DNSWL_NONE=-0.0001, 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:297258 Archived-At: On 09.10.2022 07:57, Eli Zaretskii wrote: >> 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. 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.