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: Thu, 13 Oct 2022 18:11:40 +0200 Message-ID: References: <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> <835ygqg1bh.fsf@gnu.org> <87ilkqbsp3.fsf@thornhill.no> <0ef04e1e-3f6c-31b6-4852-0c9c2c43b912@yandex.ru> <86h708ft1k.fsf@stephe-leake.org> <86bkqgdnz6.fsf@stephe-leake.org> 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="34385"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Richard Stallman , Dmitry Gutov , eliz@gnu.org, emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 13 18:24:23 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 1oj10Q-0008jN-MU for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Oct 2022 18:24:23 +0200 Original-Received: from localhost ([::1]:45868 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oj10P-0005Ii-L3 for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Oct 2022 12:24:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41978) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oj0oL-0007nR-8l for emacs-devel@gnu.org; Thu, 13 Oct 2022 12:11:53 -0400 Original-Received: from out2.migadu.com ([2001:41d0:2:aacc::]:16675) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oj0oF-0002X5-K3; Thu, 13 Oct 2022 12:11:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1665677501; 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=FWKZEUFvMVgxgz3U1k9tCZEQKDQ/BVCuoxivoZO6NGA=; b=EmuSN1Hv1QJiG5mVp3OhL7HU06iHP9cF1gywIUSfGw3/P7Y2L7dxOZEqcY2iMLAhh+Giq+ 0wjcCkdkZ+0XP/WKpzpGeCymNmslWO/2pj6DP8FnNvGPepjh5x4mRD9V4JPSqkrfi40wVh n917h9o54rVob4z40+nGev0usCwJ5nH/44BHcV86K4y+L2amvTF3+2xHtwvS7XRpe9TMpY tkGIkKVs39oWGF18En3tzhSK/Kjd/r2VkMia3fir/8mc5uJ7YRpNg1iG/rygeiwJYZu8Qg LEgMpPsP6fdRvQzZfII44tTk/0LG6/aIV+pvO5qWjZqqvvIzWqCEwWuOyTJI3Q== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <86bkqgdnz6.fsf@stephe-leake.org> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:2:aacc::; envelope-from=theo@thornhill.no; helo=out2.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:297682 Archived-At: On 13 October 2022 12:20:13 CEST, Stephen Leake wrote: >Theodor Thornhill writes: > >> On 13 October 2022 02:47:51 CEST, Stephen Leake wrote: >>>Richard Stallman writes: >>> >>>> [[[ To any NSA and FBI agents reading my email: please consider ]]= ] >>>> [[[ whether defending the US Constitution against all enemies, ]]= ] >>>> [[[ foreign or domestic, requires you to follow Snowden's example=2E = ]]] >>>> >>>> > > Because all of the interaction between server and client in lsp= is json >>>> > > there's a huge overhead with parsing and shipping things into t= he emacs >>>> > > user interface=2E So IMO what tree-sitter is good at should be= left to >>>> > > tree-sitter=2E >>> >>>Premature optimization=2E >>> >> >> Why do you say that?=20 > >Because it gives a supposed cause without evidence of an actual problem= =2E > >> I've been using lsp for a long time, and typing lag can get unbearable >> with servers that sends too much stuff=2E When 20k completions >> containing _full_ documentation for every result that json gets >> humongous=2E=20 > >Ok, that's actual data=2E On the other hand, did you measure different >parts of the process, so you are sure that the json is the bottleneck, >and not something else? It's not clear just from this description that a >tree-sitter implementation would be faster=2E > Yes I did,at the time=2E Though I cannot find the issue at hand, but it wa= s related to Elm-language-server if memory serves me right=2E=20 >In addition, LSP supports sending the documentation later, after the user >has actually looked at a completion item, using a completionItem/resolve >request=2E So this sounds like a specific client or server implementation >problem more than an inherent LSP problem=2E > Sure, but that's life=2E Nonconforming servers are everywhere, and these i= ssues are bound to happen=2E If something as important and simple as colors= and indentation would be unusable because of a bug in a transitive depende= ncy we have a much bigger problem, imo=2E Tree-sitter will not cause us the= se headaches as easily=2E=20 >> Adding syntax highlights on top of that isn't advisable, considering >> emacs nonmultithreaded nature=2E > >Syntax highlighting, mediated by font-lock, should only ever send small >amounts of data; one screen full at a time=2E That is if the server >supports the textDocument/semanticTokens/range request, and not just the >textDocument/semanticTokens/full request=2E > Yes, and yet again we are at the mercy of the specific server=2E Using tre= e-sitter we can much more reliably resolve the situation on our own=2E Of c= ourse, in both cases the tech is new and will mature, but to me tree-sitter= seems like the obvious winner=2E=20