unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Paul Michael Reilly <pmr@pajato.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Setting up language servers for Eglot
Date: Fri, 7 Aug 2020 15:32:45 +0100	[thread overview]
Message-ID: <CALDnm527SBrXZ0oj=28TFOtPysYSLrLofKsvvgYOTzhu2ddCDg@mail.gmail.com> (raw)
In-Reply-To: <CAGwjgEgDXgVG_RP_5o2Uq5aTKiW9bBnBBRXPX5wT6Ye7GYFCVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Hi Paul,

As I told you offline I am quite busy at the moment to help you with this
directly.

But if you look at Eglot's homepage you'll see that you need an entry in
`eglot-server-programs` variable.
That entry should associate a major mode with a program (the executable).
So you need a `kotlin-mode`
major mode.  Emacs doesn't come with one but you can probably get one
somewhere.  Also, earlier I
linked to an issue describing how someone got Eglot working with Kotlin
using this simple technique.
Maybe searching Eglot's bug tracker for "Kotlin" will bring you to that
issue.

Hope this helps
João

On Fri, Aug 7, 2020 at 3:28 PM Paul Michael Reilly <pmr@pajato.com> wrote:

> What is your thinking about how Users should set up language servers that
> you do not automagically set up as part of Eglot?
>
> For Kollin, it is not a simple matter, as far as I can see right now, of
> just adding an executable to a directory on the executable search path.
> Perhaps I should see how Eglot deals with Java, if at all.
>
> -pmr
>


-- 
João Távora

[-- Attachment #2: Type: text/html, Size: 1694 bytes --]

  reply	other threads:[~2020-08-07 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07 14:27 Setting up language servers for Eglot Paul Michael Reilly
2020-08-07 14:32 ` João Távora [this message]
2020-08-07 15:05   ` Paul Michael Reilly
2020-08-07 15:58     ` Yuan Fu
2020-08-07 15:59       ` João Távora
2020-08-08  5:59         ` Paul Michael Reilly

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='CALDnm527SBrXZ0oj=28TFOtPysYSLrLofKsvvgYOTzhu2ddCDg@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.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 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).