From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: Language Server Protocol Date: Sun, 26 Jul 2020 18:55:45 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000021037305ab5bebab" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32565"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: Paul Michael Reilly Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 26 19:56:44 2020 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 1jzkt8-0008LQ-Om for ged-emacs-devel@m.gmane-mx.org; Sun, 26 Jul 2020 19:56:42 +0200 Original-Received: from localhost ([::1]:47240 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jzkt7-00084m-Qv for ged-emacs-devel@m.gmane-mx.org; Sun, 26 Jul 2020 13:56:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40706) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jzksU-0007fa-AJ for emacs-devel@gnu.org; Sun, 26 Jul 2020 13:56:02 -0400 Original-Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]:33128) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jzksS-0002zn-I9 for emacs-devel@gnu.org; Sun, 26 Jul 2020 13:56:02 -0400 Original-Received: by mail-wr1-x433.google.com with SMTP id f18so12685680wrs.0 for ; Sun, 26 Jul 2020 10:55:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rqA01zl6Mmhd/eUUygePXHeTxg7DtfMX+zabMGnN1HE=; b=MCRdmLTykxvTB6+ok0olEN1Gc4qAprlu/L5PxXfcz9CKUPSkJVRv2TYtiIXFGKgTYY LF6NTSgzhZEFQJIfdDCoAqk98A5iCBZtN76GQ4N7ZRi26f7etX0ZJVaxYv3l4yFx1PoP o7qLvcPhOPNcD8XmkVeimc4ruZi5HdnI9FUpj46MeGYUhfFV9RC9JuaLsomJ1qv8Nq4H EsiySS3KtNXn40sllpeHAf5WHz0lNN7+qjkT6W34TLpD5WcwUKk1VREUZTHAUYCoRGXI YWAcO44OrgSe+aoN9+OHwWYUO58OZlh0eLzMOoSAIFPuF8kbpHRpEcZBCr2K3LQDp7IG tcAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rqA01zl6Mmhd/eUUygePXHeTxg7DtfMX+zabMGnN1HE=; b=SqE2vj9QgIXSpkCC+mZpQ090KCp/g8o+GT8reIwiOWErmObNQcsOoK2zefaiwPCpnR mp/enJ/AZIyXvTIhX/aJBllmFBk6fWg7CCRmHGUzZ6zdsrIk//1YzIWZzaiAvYjIQPnZ HIgyOuai7nyHSW5lTN/a1TjNFfk0zNEyQzn6XYEZl4A/ccC6z48rOSvf4xRB7PkOHcPO PtGcB1Nb7+OFnqA497gyOMRjHNxwjvTDso1KxdcJ1WzqsYgOke1ubPXOQTwyB7gSloS9 lXftwXi3ix+JzdMvSOmUGCvErZuO8iXwagFi77DJMopB9s2VOIJvq20gNSotfejGVRJa EBHw== X-Gm-Message-State: AOAM532goSNB//wewJ3hJ3GMYhzKgYvESMF6kLnAsNWtuDUO3ZPTq1TJ ney5ruoio/Tw8wJqL6s2fnUSvHphxQ5nmM4BH34= X-Google-Smtp-Source: ABdhPJzo/pclzCNgp4QQypSekKVFRzUHRpE25QtohK/FpO7SBOb6f46L328rBrh+5QLD2e+rw8JyfljI2A9CuJlJTIA= X-Received: by 2002:a5d:4d0b:: with SMTP id z11mr16532778wrt.315.1595786158735; Sun, 26 Jul 2020 10:55:58 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2a00:1450:4864:20::433; envelope-from=joaotavora@gmail.com; helo=mail-wr1-x433.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. 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, HTML_MESSAGE=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.23 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:253265 Archived-At: --00000000000021037305ab5bebab Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Paul, I'm the author of Eglot, an LSP client for Emacs whose functionality will soon (ish) be in Emacs itself. It explores a subset of the LSP protocol and leverages it in terms of Emacs functions. You can use Eglot it to gauge how developed a server is. You can -- and emacs-devel is the place to do that -- extend Eglot to explore more of the LSP protocol, provided that the LSP server you're using works in those regions unexplored by Eglot. Not sure if this is what you're looking for. If you're strictly looking for a list of capabilities offered by the LSP server in question, there is a section in the protocol specification devoted to describing a protocol message with that information. That protocol message is sent early on in the handshake, and you can easily inspect it with the Eglot client (or other clients). Using Emacs or other clients for this specific purpose would be mostly "indifferent" in your categorization. Jo=C3=A3o On Sun, Jul 26, 2020, 16:51 Paul Michael Reilly wrote: > I am looking for an LSP expert who can tell me if the notion of using > Emacs to learn what kinds of capabilities a particular LSP server (Kotlin= ) > provides is a good, bad or indifferent idea. Seems like someone here migh= t > be such a person. > > -pmr > --00000000000021037305ab5bebab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Paul,

I&#= 39;m the author of Eglot, an LSP client for Emacs whose functionality will = soon (ish) be in Emacs itself. It explores a subset of the LSP protocol and= leverages it in terms of Emacs functions. You can use Eglot it to gauge ho= w developed a server is. You can -- and emacs-devel is the place to do that= -- extend Eglot to explore more of the LSP protocol, provided that the LSP= server you're using works in those regions unexplored by Eglot.=C2=A0 = Not sure if this is what you're looking for.
If you're strictly looking for a list of capab= ilities offered by the LSP server in question, there is a section in the pr= otocol specification devoted to describing a protocol message with that inf= ormation. That protocol message is sent early on in the handshake, and you = can easily inspect it with the Eglot client (or other clients). Using Emacs= or other clients for this specific purpose would be mostly "indiffere= nt" in your categorization.

Jo=C3=A3o

On Sun, Jul 26, 2020, 16:51 Paul Michael Reilly &l= t;pm= r@pajato.com> wrote:
I am looking for an LSP expert who can tell me if the notion of u= sing Emacs to learn what kinds of capabilities a particular LSP server (Kot= lin) provides is a good, bad or indifferent idea. Seems like someone here m= ight be such a person.

-pmr
--00000000000021037305ab5bebab--