unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Niall Dooley <dooleyn@gmail.com>, 67442@debbugs.gnu.org
Subject: bug#67442: [PATCH] eglot: Add ruff-lsp as an alternative python server
Date: Sat, 25 Nov 2023 12:39:22 +0000	[thread overview]
Message-ID: <CALDnm53Nzn_Qm9hZhOEPRjCG3BePik9WUZWKNK9KJrNJRWYOdg@mail.gmail.com> (raw)
In-Reply-To: <83fs0uccoj.fsf@gnu.org>

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

On Sat, Nov 25, 2023, 11:09 Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Niall Dooley <dooleyn@gmail.com>
> > Date: Fri, 24 Nov 2023 23:42:28 +0100
> >
> > 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.
>
> What do you mean by "alongside"?
>
> João, does Eglot support such "alongside" servers?
>

No. This is a feature on my to-do list, but alas I haven't had time to work
on it.

João

>

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

  parent reply	other threads:[~2023-11-25 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 22:42 bug#67442: [PATCH] eglot: Add ruff-lsp as an alternative python server Niall Dooley
2023-11-25  9:19 ` Eli Zaretskii
2023-11-25 11:09 ` Eli Zaretskii
2023-11-25 11:19   ` Niall Dooley
2023-11-25 12:39   ` João Távora [this message]
2023-11-25 13:00     ` Eli Zaretskii
2023-11-26  9:53       ` João Távora
2023-11-27 10:22         ` Niall Dooley

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=CALDnm53Nzn_Qm9hZhOEPRjCG3BePik9WUZWKNK9KJrNJRWYOdg@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=67442@debbugs.gnu.org \
    --cc=dooleyn@gmail.com \
    --cc=eliz@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).