GNU bug report logs - #59214
[PATCH] Alternate rust-analyzer command added

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pankaj Jangid <pankaj <at> codeisgreat.org>
Cc: 59214 <at> debbugs.gnu.org, hello+emacs <at> miangraham.com, joaotavora <at> gmail.com
Subject: bug#59214: [PATCH] Alternate rust-analyzer command added
Date: Fri, 18 Nov 2022 10:29:25 +0200

> From: Pankaj Jangid <pankaj <at> codeisgreat.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  "M. Ian Graham"
>  <hello+emacs <at> miangraham.com>,  59214 <at> debbugs.gnu.org
> Date: Fri, 18 Nov 2022 10:43:02 +0530
> 
> João Távora <joaotavora <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.