all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: emacs-devel@gnu.org
Subject: Language Servers and Emacs
Date: Tue, 11 Apr 2017 12:28:16 -0400	[thread overview]
Message-ID: <20170411122816.751a130f@jabberwock.cb.piermont.com> (raw)

Microsoft has invented an interesting new protocol for IDEs
and code editors to talk to language tools (like compilers) to do
things like smart autocompletion, jumping to code definitions, and the
like.

The idea is that compilers and similar tools generally know a lot
about the structure of a language and can provide help to an editor as
an external service, so the editor doesn't need to handle parsing,
symbol tables, etc. for the language on its own. The editor can just
ask the compiler or language tool for the information when it needs
it.

The protocol is open and they have no intellectual property claims on
it. It is JSON based and should be straightforward to support.

A general description is at:

http://langserver.org/

And detailed protocol information is at:

https://github.com/Microsoft/language-server-protocol

It was originally designed for their "Roslyn" C# compiler (which is
free software, it's Apache licensed) to integrate with their own
editors and IDEs, but other compiler projects and editors seem to be
adopting the thing. There are now language servers people have built
for a lot of languages, and there's support appearing for the
protocol in a bunch of editors.

I'm mentioning this here because I think the Emacs community would be
interested in this capability, though I suspect that it would also be
really neat if GCC developed a language server for C and C++.

I recall that a while ago, RMS had a lot of problems with the idea
of opening up GCC in ways that might have made it possible for people
to use it too much for proprietary compilers. Using the Language
Server Protocol, it should be possible for GCC and other free
language tools to talk to a variety of IDEs and Editors (including, I
hope, Emacs) to allow advanced modern code editing _without_ the
sorts of risks he was worried about.

Perry
-- 
Perry E. Metzger		perry@piermont.com



             reply	other threads:[~2017-04-11 16:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 16:28 Perry E. Metzger [this message]
2017-04-11 16:36 ` Language Servers and Emacs 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
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=20170411122816.751a130f@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=emacs-devel@gnu.org \
    /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.