all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Perry E. Metzger" <perry@piermont.com>
Cc: Helmut Eller <eller.helmut@gmail.com>, emacs-devel@gnu.org
Subject: Re: Language Servers and Emacs
Date: Tue, 25 Apr 2017 13:17:37 +0100	[thread overview]
Message-ID: <87h91cvfz2.fsf@russet.org.uk> (raw)
In-Reply-To: <20170412085909.44faf429@jabberwock.cb.piermont.com> (Perry E. Metzger's message of "Wed, 12 Apr 2017 08:59:09 -0400")

"Perry E. Metzger" <perry@piermont.com> writes:

>> So it seems likely that Clang will support the protocol long before
>> GCC does.  It might also have political implications if Emacs
>> implements the client side if Clang is the only server for C/C++.
>
> There are servers for many other languages too, this is not a C/C++
> only issue. (And I think GCC needs to gain this capability in any
> case, it appears that it is being rapidly adopted. There are now
> langserv implementations for dozens of languages -- Python, Java, PHP,
> Go, Rust, Swift, JavaScript, C#, Julia, Scala, and the list goes on,
> plus there are a bunch of IDEs adopting the protocol too, and support
> for the vim and Atom editors are coming.)
>
> Architecturally, this is certainly the right thing. One would
> generally far prefer to have the language implementation help the
> editor with parsing than have to re-implement parsing inside the
> editor.


Apologies for the zombie posting -- easter holidays and all.

It would be interesting to do a comparison with "nrepl" which is the
protocol that CIDER, the emacs package for clojure, uses. This is pretty
feature complete now and it would give an good side-by-side
comparison. I think that ENSIME (for Scala) has a protocol in there as
well.

I agree with you, having a standard to use is a very good thing.

Phil



  reply	other threads:[~2017-04-25 12:17 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 [this message]
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=87h91cvfz2.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=perry@piermont.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.