unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "M. Ian Graham" <hello+emacs@miangraham.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59214@debbugs.gnu.org, pankaj@codeisgreat.org, joaotavora@gmail.com
Subject: bug#59214: [PATCH] Alternate rust-analyzer command added
Date: Thu, 17 Nov 2022 19:43:39 +0000	[thread overview]
Message-ID: <E_R7SPW_eYFCpJvnjymRLT9ebxiA9NoHrHMbzwlISXk0EdYdYK78L4-saly-BY8Pq-N4-RoqNoExGMG2HUK_Pyqg-FKzWzN9edn-VsUhgAk=@miangraham.com> (raw)
In-Reply-To: <83o7t5ct9j.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> wrote:

> 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.

Completely agreed. I don't think there's a great way to support most Rust devs in a stable Emacs release besides treating Rust like any other language, deferring to normal environment settings, and letting individuals, their configs, and their outside libraries cross the thrash gap to fix defvars, envvars, and other settings as needed.

> 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.

This, however, also sounds like a great enabler to me. Rust devs would gain the option of easily matching the change velocity in their elisp config rather than through env vars, which would probably improve the case of Windows users that Pankaj brought up earlier.

Apologies to the participants for my jumping all over this thread. I'm absolutely in support of improving the new Rust dev experience if Emacs can do it without painting itself into a corner. Rust has a lot of paint. :)

Cheers,
Ian






  reply	other threads:[~2022-11-17 19:43 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 [this message]
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='E_R7SPW_eYFCpJvnjymRLT9ebxiA9NoHrHMbzwlISXk0EdYdYK78L4-saly-BY8Pq-N4-RoqNoExGMG2HUK_Pyqg-FKzWzN9edn-VsUhgAk=@miangraham.com' \
    --to=hello+emacs@miangraham.com \
    --cc=59214@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).