From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Sun, 09 Oct 2022 18:56:59 +1100 Message-ID: <86bkqlh0wc.fsf@gmail.com> 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 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17031"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.9.0; emacs 29.0.50 Cc: rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 09 10:13:02 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 1ohRQh-00049i-HK for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 10:12:59 +0200 Original-Received: from localhost ([::1]:58334 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ohRQg-0002mn-4n for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 04:12:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48408) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohRPU-0001zb-04 for emacs-devel@gnu.org; Sun, 09 Oct 2022 04:11:44 -0400 Original-Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]:42965) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ohRPS-00033F-C2; Sun, 09 Oct 2022 04:11:43 -0400 Original-Received: by mail-pj1-x1033.google.com with SMTP id l1-20020a17090a72c100b0020a6949a66aso8081394pjk.1; Sun, 09 Oct 2022 01:11:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:from:to:cc:subject:date:message-id:reply-to; bh=3XTFVyKxUskM8zujKszsKSTJXgOSxRtjTCsyiVg9g/8=; b=qCYIuYqKYfZc/fNbmUyjjiVKaranB6qTEfXruB04hxStg6IJXuGKXxwllzBe4QvPtM IgpAq5zkkkirnzM2BYOaloLdoRQg+A/01OCbOtO9QkGQYqpx6jR/DCopTYUlOb7GXhbl sqUILEP6RO7EWJxS0n+VdypivfVd3Hf3tuwO7Ag7v6Lwzaif/G0LrewU4Umnzw9sQi4W Z8nIwr0Yr1TFh2h8o7zoLmn1mt33+8GaOfaeurQKn9sA7nLkb70tnHIJ5uEqyVEGrVA8 0wt1Gwv3lWW4yRsIPZFTlscbTSUrZrfe62jGwsUZY2lDHGo12wHt18zewdT99FJaD7pG Rt9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:cc:to:from :user-agent:references:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=3XTFVyKxUskM8zujKszsKSTJXgOSxRtjTCsyiVg9g/8=; b=1XFuxo0kNQIE9DpHmNyCdnlKtKL5sEsvjnsSXHy5oZDIKHylh9OrC5guXjt+nRtSHK G5Mt7avItiu90jft1KPM4KKtXo3OK632QJSPzmdo7I+f+TiEQtPJn0BCjmevyOunZrUs NJSD3N9NVJjo6aJJRoIf3DqDmmnTRGnOjFKy4ixiBc2mamwrHbbyfRawNgNxBviXtaYj KLi2N7MC7cELFs1mdwL5xLhxnCqlJTEP2IUwtFlulK9CTEN7Oylhgnhr00XcUVjkRVa9 Qjr2PVhOCTJSQOBzbmB2NQIcpavnJm85XTYi2wkYzW+Y8/U1rMgdR2nX0f6oQ60OMLxM 9NEQ== X-Gm-Message-State: ACrzQf2rhA0JwvW9By1kAe/sBQaPotkwxx8ccYru16M5UQPmwrEF3Wg6 BuPXTnqug4t4bBKDez5tj18qB5m8YPA= X-Google-Smtp-Source: AMsMyM7qJLZiaiUmfvhxNidVVtJBMoQptfrlkOVJ6plyH7zuPmr9OK3lfHm2Hp7DRurmJRWVxD00iA== X-Received: by 2002:a17:903:234c:b0:17f:a253:b538 with SMTP id c12-20020a170903234c00b0017fa253b538mr13211806plh.110.1665303099458; Sun, 09 Oct 2022 01:11:39 -0700 (PDT) Original-Received: from dingbat (124-169-22-230.dyn.iinet.net.au. [124.169.22.230]) by smtp.gmail.com with ESMTPSA id b23-20020aa79517000000b00562eff85594sm2469417pfp.121.2022.10.09.01.11.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 09 Oct 2022 01:11:36 -0700 (PDT) In-reply-to: <83fsfxk30x.fsf@gnu.org> Received-SPF: pass client-ip=2607:f8b0:4864:20::1033; envelope-from=theophilusx@gmail.com; helo=mail-pj1-x1033.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, 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:297245 Archived-At: Eli Zaretskii writes: >> 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"). To add to the complexity, 'best' will depend heavily on the LSP language server being used. Some servers are more feature rich than others and some are better implementations than others. For example, I changed the language server I use with Javascript as I found a different one from that being used by most LSP clients which was faster and handled indentation 'better'. I can imagine there will be situations/languages where tree-sitter does a better job than the currently existing LSP servers for that language. Whatever the default is, the user will need the easy ability to select which functionality is provided by which package.