From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 60089@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#60089: 29.0.60; eglot doesn't support csharp-ls language server [PATCH]
Date: Thu, 15 Dec 2022 22:49:39 +0100 [thread overview]
Message-ID: <49A0AC5D-0191-4D92-9B29-06BB086725AE@secure.kjonigsen.net> (raw)
In-Reply-To: <CADwFkmk=wGwkHB5bVFfzvbFKB4KrW-p2dTLLj6vD4v_VfGTAYA@mail.gmail.com>
On 15 Dec 2022, at 22:28, Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
>
>> Right now eglot only knows about the Omnisharp Roslyn language server
>> for C#.
>>
>> csharp-ls[1] is another popular language server and is supported by
>> other LSP-clients, like lsp-mode.
>>
>> Eglot should support it too.
>>
>> Attached is a patch which introduces support for this language-server.
>>
>> [1] https://github.com/razzmatazz/csharp-language-server
>
> Could you give a rationale for why we should prefer omnisharp over
> csharp-ls? Why not the other way around?
>
> (I know nothing about C#.)
As far as presedence go, I have no personal preference here.
I myself use csharp-ls, because it’s faster, but it’s newer with less lineage and only aims to support new “.net core” type projects.
Omnisharp is not as fast, but has been around for a longer time and officially also supports “legacy”-style .net framework projects.
As such it probably make sense to present Omnisharp as the default, since it offers the highest compatibility guarantees regardless of target code-base.
—
Jostein Kjønigsen
https://jostein.kjønigsen.net
next prev parent reply other threads:[~2022-12-15 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 12:55 bug#60089: 29.0.60; eglot doesn't support csharp-ls language server [PATCH] Jostein Kjønigsen
2022-12-15 21:28 ` Stefan Kangas
2022-12-15 21:49 ` Jostein Kjønigsen [this message]
2022-12-16 2:24 ` Stefan Kangas
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=49A0AC5D-0191-4D92-9B29-06BB086725AE@secure.kjonigsen.net \
--to=jostein@secure.kjonigsen.net \
--cc=60089@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=stefankangas@gmail.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.