From: Dimitri Belopopsky <dimitri@belopopsky.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60761@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
joaotavora@gmail.com
Subject: bug#60761: [PATCH] Remove deprecated RLS server from list of eglot servers
Date: Fri, 13 Jan 2023 08:36:51 +0100 [thread overview]
Message-ID: <CA+46MXbamyxxwYzyQuWq7Gy7zRX83_1fxG7yqrkLHf8cAS8Ffw@mail.gmail.com> (raw)
In-Reply-To: <83v8laaon9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Fri, 13 Jan 2023, 08:19 Eli Zaretskii, <eliz@gnu.org> wrote:
> > Cc: João Távora <joaotavora@gmail.com>
> > From: Stefan Kangas <stefankangas@gmail.com>
> > Date: Thu, 12 Jan 2023 17:15:42 -0800
> >
> > Dimitri Belopopsky <dimitri@belopopsky.com> writes:
> >
> > > I'm suggesting removing RLS from the server list in eglot, as it is
> > > currently not maintained anymore by the Rust developers.
> > > The github was archived: https://github.com/rust-lang/rls
> >
> > Thanks, pushed to master (commit f1310859a0d).
>
> Does "not maintained anymore by the Rust developers" necessarily mean
> it is wrong to use it? Having the server mentioned in the DB doesn't
> mean we force the users to use it, just that we support it if the user
> has it installed.
>
In the general case I think I agree.
Here, it is explicitely stated that users should move to rust-analyzer.
There is nothing wrong in using it anyway,
but I don't think it should be encouraged to use in this case.
> João, WDYT? I guess we should to have some criteria for when to
> remove servers from the DB?
>
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
next prev parent reply other threads:[~2023-01-13 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:43 bug#60761: [PATCH] Remove deprecated RLS server from list of eglot servers Dimitri Belopopsky
2023-01-13 1:15 ` Stefan Kangas
2023-01-13 7:18 ` Eli Zaretskii
2023-01-13 7:36 ` Dimitri Belopopsky [this message]
2023-01-13 17:51 ` João Távora
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=CA+46MXbamyxxwYzyQuWq7Gy7zRX83_1fxG7yqrkLHf8cAS8Ffw@mail.gmail.com \
--to=dimitri@belopopsky.com \
--cc=60761@debbugs.gnu.org \
--cc=eliz@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 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).