From: "João Távora" <joaotavora@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Niall Dooley <dooleyn@gmail.com>, 67441@debbugs.gnu.org
Subject: bug#67441: [PATCH] eglot: Add ruff-lsp as an alternative python server
Date: Fri, 15 Dec 2023 01:29:42 +0000 [thread overview]
Message-ID: <CALDnm52XxMPNosB8af4507NUgDBSwdjm0ByEEo2Q_i52dZ95+Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnEf6irDR_yHoi3k5t5s4WZgVwCq9GTqb7izjHP1K1Gvw@mail.gmail.com>
On Fri, Dec 15, 2023 at 1:22 AM Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Niall Dooley <dooleyn@gmail.com> writes:
>
> > ruff-lsp [1] is a Language Server Protocol implementation for Ruff [2,
> > 3], an extremely fast Python linter and code formatter, written in
> > Rust.
> >
> > It supports surfacing Ruff diagnostics and providing Code Actions to
> > fix them, but is intended to be used alongside another Python LSP in
> > order to support features like navigation and autocompletion.
> >
> > [1]: https://github.com/astral-sh/ruff-lsp
> > [2]: https://github.com/astral-sh/ruff
> > [3]: https://docs.astral.sh/ruff/
>
> João, any comments here? Does eglot support running more than one LSP
> server at the same time?
No. This is the same question of Eli, who phrased it "alongside".
> AFAICT, pylsp (for example) has built-in support for ruff, so while I'm
> sure there's a use case for ruff-lsp, I don't think I currently
> understand it.
Me neither. The fact that some language servers (pylsp, clangd) already
do what the hypothetical Eglot feature for running servers alongside each
other would do, is also the main reason why that feature has lost some
(definitely not all) of its relevance.
> In any case, I think the patch seems harmless enough, and could probably
> be installed as-is.
Agree. Install at will.
João
next prev parent reply other threads:[~2023-12-15 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 15:52 bug#67441: [PATCH] eglot: Add ruff-lsp as an alternative python server Niall Dooley
2023-12-15 1:22 ` Stefan Kangas
2023-12-15 1:29 ` João Távora [this message]
2023-12-16 11:12 ` 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=CALDnm52XxMPNosB8af4507NUgDBSwdjm0ByEEo2Q_i52dZ95+Q@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=67441@debbugs.gnu.org \
--cc=dooleyn@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.