From: Eli Zaretskii <eliz@gnu.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 59214@debbugs.gnu.org, hello+emacs@miangraham.com, joaotavora@gmail.com
Subject: bug#59214: [PATCH] Alternate rust-analyzer command added
Date: Fri, 18 Nov 2022 10:29:25 +0200 [thread overview]
Message-ID: <83y1s8br8a.fsf@gnu.org> (raw)
In-Reply-To: <87a64oj15t.fsf@codeisgreat.org> (message from Pankaj Jangid on Fri, 18 Nov 2022 10:43:02 +0530)
> From: Pankaj Jangid <pankaj@codeisgreat.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, "M. Ian Graham"
> <hello+emacs@miangraham.com>, 59214@debbugs.gnu.org
> Date: Fri, 18 Nov 2022 10:43:02 +0530
>
> João Távora <joaotavora@gmail.com> writes:
>
> >> FWIW, I think Rust is too crazy for us to follow its daily changes and
> >> offer support for its server OOTB in eglot-server-programs. Emacs is
> >> not equipped to follow such frequent and radical changes. If we want
> >> to make this seamless for users of Rust, we should provide a special
> >> command to update eglot-server-programs with whatever it is the latest
> >> Rust fashion. Or maybe we should even leave that to Rust mode.
> >>
> >
> > Yes, indeed, my thoughts exactly, especially this last bit.
> >
>
> Agree.
>
> And thank you, Ian, for bringing up the counter thoughts in the
> discussion. It was an eye opener for me. I was thinking `rustup' is the
> only way to use `rust'.
So what's the bottom line here? Do we need to make any change in
eglot.el, and if so, what change is that?
next prev parent reply other threads:[~2022-11-18 8:29 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
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 [this message]
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=83y1s8br8a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59214@debbugs.gnu.org \
--cc=hello+emacs@miangraham.com \
--cc=joaotavora@gmail.com \
--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).