From: "João Távora" <joaotavora@gmail.com>
To: "M. Ian Graham" <hello+emacs@miangraham.com>
Cc: 59214@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
pankaj@codeisgreat.org
Subject: bug#59214: [PATCH] Alternate rust-analyzer command added
Date: Thu, 17 Nov 2022 08:19:57 +0000 [thread overview]
Message-ID: <CALDnm53qD3LYW67U_3EhQqFqE6qUyXD+gokqOu8HKpOdwqQ0Hg@mail.gmail.com> (raw)
In-Reply-To: <NU4UkMhlLNclWtPfskgK9pUG6UZHlI0yXhM3rZ5u0Du6DAs8_HEBlQ5SpiodXpaeOpTB3haLUHkEkB4GHmSqPTLPjdxirhu37N0xu5L-mZ8=@miangraham.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Thu, Nov 17, 2022 at 8:12 AM M. Ian Graham <hello+emacs@miangraham.com>
wrote:
>
> If we're adding a new dependency on an optional installation method, can
> we also please retain the "add rust-analyzer to PATH and eglot will just
> work" current behavior as well?
>
So rustup is just an optional way of installing rust-analyzer? If so I
think we shouldn't
tweak this.
João
(tangent: rustup being optional is intriguing and interesting. If I wanted
to learn Rust, just Rust, should I start with a rustup-less setup?)
[-- Attachment #2: Type: text/html, Size: 947 bytes --]
next prev parent reply other threads:[~2022-11-17 8:19 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
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 [this message]
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=CALDnm53qD3LYW67U_3EhQqFqE6qUyXD+gokqOu8HKpOdwqQ0Hg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=59214@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hello+emacs@miangraham.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).