all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Paul Michael Reilly <pmr@pajato.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Language Server Protocol
Date: Sun, 26 Jul 2020 18:55:45 +0100	[thread overview]
Message-ID: <CALDnm52fF4WS0cV9zLy+2ce0437-_i2uEdco8biYzJz-qfc3nQ@mail.gmail.com> (raw)
In-Reply-To: <CAGwjgEh+4K2wCtcSsvuO9ePqujLxHfg9XC-U=xN5ye0ssw5RJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

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ão

On Sun, Jul 26, 2020, 16:51 Paul Michael Reilly <pmr@pajato.com> 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 might
> be such a person.
>
> -pmr
>

[-- Attachment #2: Type: text/html, Size: 1852 bytes --]

  reply	other threads:[~2020-07-26 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 15:50 Language Server Protocol Paul Michael Reilly
2020-07-26 17:55 ` João Távora [this message]
2020-07-27  3:10   ` Richard Stallman
2020-07-27  7:24     ` João Távora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALDnm52fF4WS0cV9zLy+2ce0437-_i2uEdco8biYzJz-qfc3nQ@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.