unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lele Gaifax <lele@metapensiero.it>
To: emacs-devel@gnu.org
Subject: Re: Language Servers and Emacs
Date: Fri, 14 Apr 2017 11:06:27 +0200	[thread overview]
Message-ID: <87bmrzs6i4.fsf@nautilus> (raw)
In-Reply-To: CA+T2Sh2R3MTrX9+UeRF0Uki2YCCAmiv8Bm3sP0PbC1vJvbJXsg@mail.gmail.com

Vibhav Pant <vibhavp@gmail.com> writes:

> 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).

Indeed it is very nice: I gave it a shot on a Python project, and will surely
try it again.

One thing that surprised me is that it asks about launching the underlying
"pyls" tool once for each visited source: is that right? As my project has
hundreds of Python modules, wouldn't that put Emacs under pressure?

One minor observation on the lisp sources: I think it's not necessary to
explicitly quote lambdas as in the following snippet

  (lsp-define-client 'python-mode "python" 'stdio #'(lambda () default-directory)
    :command '("pyls")
    :name "Python Language Server")

Thank you,
ciao, lele.
-- 
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it  |                 -- Fortunato Depero, 1929.




  reply	other threads:[~2017-04-14  9:06 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
2017-04-14  9:06       ` Lele Gaifax [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87bmrzs6i4.fsf@nautilus \
    --to=lele@metapensiero.it \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).