From: Vibhav Pant <vibhavp@gmail.com>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Language Servers and Emacs
Date: Thu, 13 Apr 2017 11:49:01 +0530 [thread overview]
Message-ID: <CA+T2Sh2R3MTrX9+UeRF0Uki2YCCAmiv8Bm3sP0PbC1vJvbJXsg@mail.gmail.com> (raw)
In-Reply-To: <20170412090739.7ee9f671@jabberwock.cb.piermont.com>
On Wed, Apr 12, 2017 at 6:37 PM, Perry E. Metzger <perry@piermont.com> wrote:
> That looks very cool! However, your warning on the web site
> makes it sound like it is not ready to be used. (I.e. you say "This
> package is still under development, and is not recommended for daily
> use.") Is that just an abundance of caution?
In some ways, yes. lsp-mode still has issues with *some* language server
(the Python one is the most mature one AFAIK, and works just fine).
> And how hard is it to add support for other clients/languages besides
> Go and Rust? (Some instructions in the repository might make it
> easier for people to help bringing this up to speed...)
>
I've updated the list of supported languages on the README. Adding
supporting for other languages is rather easy, you just need to tell
lsp-mode about how the language server connects and communicates
with clients. The remaining is handled by the package itself. For instance,
this is how Python is supported:
https://github.com/vibhavp/emacs-lsp/blob/c7c6a477b0c8aff1ce8aa032992cd10085ee0143/lsp-mode.el#L92
--
Vibhav Pant
vibhavp@gmail.com
next prev parent reply other threads:[~2017-04-13 6:19 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
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 [this message]
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=CA+T2Sh2R3MTrX9+UeRF0Uki2YCCAmiv8Bm3sP0PbC1vJvbJXsg@mail.gmail.com \
--to=vibhavp@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.