From: "Perry E. Metzger" <perry@piermont.com>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: Helmut Eller <eller.helmut@gmail.com>,
Katherine Cox-Buday <cox.katherine.e@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Language Servers and Emacs
Date: Wed, 26 Apr 2017 09:24:24 -0400 [thread overview]
Message-ID: <20170426092424.61c925c5@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <87tw5b4dyw.fsf@russet.org.uk>
On Wed, 26 Apr 2017 12:15:19 +0100 phillip.lord@russet.org.uk
(Phillip Lord) wrote:
> > I suspect that most of the ways of interacting with external
> > language tools other than LSP will fade over time, but whether or
> > not that's the case, it clearly seems to be smarter to have an
> > external language tool than to have to duplicate the work of
> > parsing and managing symbol tables inside the editor.
>
> Well, this depends whether LSP is good or not.
You might re-read what I was saying. It is more general than LSP. My
point was that whether _LSP_ is the One True Way or not, the idea of
interacting with language tools to get information about the program
instead of building a parser for every language into the editor is
clearly a good one. So that doesn't depend on whether LSP is good or
not. :)
> Even then, history
> suggests that introduction of the one true standard, just results
> in yet another technique for the same thing.
>
> A brief look at LSP seems that it's relatively limited in scope,
> though; it has some discussion of "capabilities" and "execute
> command". How extensible is it? For instance, NREPL allows evalling
> code, or loading files? Would it be possible to send enough data
> through LSP to support edebug step through debugging for instance?
It's really intended for helping editors out, but it is extensible.
Have a read:
https://github.com/Microsoft/language-server-protocol
https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2017-04-26 13:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 16:28 Language Servers and Emacs Perry E. Metzger
2017-04-11 16:36 ` Philippe Vaucher
2017-04-11 16:44 ` Perry E. Metzger
2017-04-11 19:32 ` Evgeniy Dushistov
2017-04-11 18:32 ` Eli Zaretskii
2017-04-12 7:39 ` Helmut Eller
2017-04-12 12:59 ` Perry E. Metzger
2017-04-25 12:17 ` Phillip Lord
2017-04-25 23:06 ` Katherine Cox-Buday
2017-04-26 2:00 ` Perry E. Metzger
2017-04-26 11:15 ` Phillip Lord
2017-04-26 12:14 ` Helmut Eller
2017-04-26 13:24 ` Perry E. Metzger [this message]
2017-04-26 15:23 ` Phillip Lord
2017-04-26 17:14 ` Richard Stallman
2017-04-27 18:15 ` Perry E. Metzger
2017-04-27 23:56 ` Richard Stallman
2017-04-12 9:03 ` Vibhav Pant
2017-04-12 13:07 ` Perry E. Metzger
2017-04-13 6:19 ` Vibhav Pant
2017-04-14 9:06 ` Lele Gaifax
2017-04-13 13:58 ` Richard Stallman
2017-04-20 10:52 ` Philipp Stephani
2017-04-21 2:08 ` Richard Stallman
2017-04-21 12:42 ` Perry E. Metzger
2017-04-21 3:44 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2018-08-30 15:51 Sébastien Gendre
2018-08-30 15:58 ` Tom Tromey
2018-08-31 4:12 ` Jay Kamat
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=20170426092424.61c925c5@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=cox.katherine.e@gmail.com \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.