From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59214@debbugs.gnu.org, Pankaj Jangid <pankaj@codeisgreat.org>
Subject: bug#59214: [PATCH] Alternate rust-analyzer command added
Date: Wed, 16 Nov 2022 17:14:11 +0000 [thread overview]
Message-ID: <CALDnm52rJDumc2jezttqBYb5torYEvz4SVyz7EDbTF+VrxAu2A@mail.gmail.com> (raw)
In-Reply-To: <83leoag78l.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
On Wed, Nov 16, 2022, 17:05 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Pankaj Jangid <pankaj@codeisgreat.org>
> > Date: Sat, 12 Nov 2022 17:23:19 +0530
> >
> > * lisp/progmodes/eglot.el (eglot-server-programs): There are two
> > ways to run rust-analyzer. After adding the rustup component,
> > users can add rust-analyzer to path and run rust-analyzer directly
> > or they may run ``rustup run stable rust-analyzer'' command. This
> > revision adds the 2nd command to the list of server programs.
> > ---
> > lisp/progmodes/eglot.el | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lisp/progmodes/eglot.el b/lisp/progmodes/eglot.el
> > index 63ebbe6cab..f54c2d2c3a 100644
> > --- a/lisp/progmodes/eglot.el
> > +++ b/lisp/progmodes/eglot.el
> > @@ -181,7 +181,7 @@ eglot-alternatives
> > when probe return (cons probe args)
> > finally (funcall err)))))))
> >
> > -(defvar eglot-server-programs `((rust-mode . ,(eglot-alternatives
> '("rust-analyzer" "rls")))
> > +(defvar eglot-server-programs `((rust-mode . ,(eglot-alternatives
> '("rust-analyzer" ("rustup" "run" "stable" "rust-analyzer") "rls")))
> > (cmake-mode . ("cmake-language-server"))
> > (vimrc-mode . ("vim-language-server"
> "--stdio"))
> > (python-mode
> > --
> > 2.30.2
>
> João, what is the procedure for handling the submissions such as this
> one? Should we ping you and wait for your decision, or are you okay
> with installing such additions based on our own judgment?
>
Additions of servers in eglot-server-programs can be installed freely
according to your judgement. Deletions and replacements based on reports of
stale/unmaintained/deprecated servers as well, but feel free to ping me.
Here, we would need and rust expert to explain why the the middle entry is
different or more useful than the first one. I'm not that expert, but
Pankaj's rationale looks reasonably sane. So maybe delete the simple
"rust-analyzer" one? Or maybe not. But two entries for the same server
looks odd. As i said, this must be looked at by someone with knowledge of
rust toolchain and configuration idioms.
João
>
[-- Attachment #2: Type: text/html, Size: 3354 bytes --]
next prev parent reply other threads:[~2022-11-16 17:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 11:53 bug#59214: [PATCH] Alternate rust-analyzer command added Pankaj Jangid
2022-11-12 12:03 ` Eli Zaretskii
2022-11-12 12:22 ` Pankaj Jangid
2022-11-12 12:51 ` Eli Zaretskii
2022-11-12 13:09 ` Pankaj Jangid
2022-11-16 17:05 ` Eli Zaretskii
2022-11-16 17:14 ` João Távora [this message]
2022-11-16 19:31 ` Eli Zaretskii
2022-11-16 21:06 ` João Távora
2022-11-17 0:12 ` Stefan Kangas
2022-11-17 5:59 ` Pankaj Jangid
2022-11-17 5:57 ` Pankaj Jangid
2022-11-17 8:13 ` João Távora
2022-11-17 10:18 ` Pankaj Jangid
2022-11-17 10:52 ` M. Ian Graham
2022-11-17 12:51 ` Pankaj Jangid
2022-11-17 18:11 ` M. Ian Graham
2022-11-17 18:20 ` Pankaj Jangid
2022-11-17 18:47 ` Eli Zaretskii
2022-11-17 19:43 ` M. Ian Graham
2022-11-17 21:49 ` João Távora
2022-11-18 5:13 ` Pankaj Jangid
2022-11-18 8:29 ` Eli Zaretskii
2022-11-18 8:44 ` João Távora
2022-11-17 8:11 ` M. Ian Graham
2022-11-17 8:19 ` João Távora
2022-11-17 9:01 ` M. Ian Graham
2022-11-17 9:07 ` João Távora
2022-11-17 10:32 ` Pankaj Jangid
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=CALDnm52rJDumc2jezttqBYb5torYEvz4SVyz7EDbTF+VrxAu2A@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=59214@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pankaj@codeisgreat.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).