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: Sun, 09 Oct 2022 08:07:01 +0200 Message-ID: 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 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6410"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org, Eli Zaretskii , rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 09 08:08:44 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 1ohPUR-0001Rv-JD for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 08:08:43 +0200 Original-Received: from localhost ([::1]:35426 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ohPUP-0005Au-1y for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Oct 2022 02:08:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37298) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohPTU-0004VK-Jb for emacs-devel@gnu.org; Sun, 09 Oct 2022 02:07:44 -0400 Original-Received: from out2.migadu.com ([188.165.223.204]:41601) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohPTS-0008I2-L5; Sun, 09 Oct 2022 02:07:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1665295656; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=U8A0DHeGrjLB5uzbLD4uuXR2Px5czwGj3SoDwhVXycU=; b=nhQ0OYSdsSdvPL+HYzIRCEndRaaATf1p07xdaGTbStUT3ONYQnJQYGSmKCC5eENNeUq7a6 F8AhTjemBqbfjTeCZZPN6/Ew2SqYNBAQR74RGBvl9nPG31mV+WquGArRpdjumal5uHd/Va yyZGaoZ6gtl0Yz5YkYET4HsD/IZzoMEKBe3dc0+PKMeR+P9sirC2o8JPxMvnnoh7a+Jful ZQpi6cYPdzqziFH+JxQ+6x4umTFvXQDam/qnDnHebw7Z47RdloGXaklZUg59RdQOW5vGlw XAkMVh2ed7iFpJqx9IvFSPJpcS7uOTyhmFtJk7b8oeUz3m80bKexo3LY1cXfsg== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <83fsfxk30x.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=188.165.223.204; envelope-from=theo@thornhill.no; helo=out2.migadu.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, 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:297244 Archived-At: >> 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=2E > >For example, at least up-front, it sounds like the LSP specification >supports both fontifications and indentation=2E 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=2E > >So, at least in principle, the functionalities based on these two >could overlap=2E 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")=2E > I'm not sure putting all of this behind json parsing is the best idea=2E I= n the case where a server can produce 30k completion per keystroke, adding = in font lock for a file of 15k lines is begging for trouble=2E Not to menti= on all the other stuff jsonrpc returns in in the meantime=2E=20 This ends very quickiy in unresponsive emacs per keystroke