all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk
To: rms@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	alexandermsummers@gmail.com, 42991@debbugs.gnu.org
Subject: bug#42991: Rust support
Date: Tue, 25 Aug 2020 11:53:49 +0100	[thread overview]
Message-ID: <bfc318aadfefaef1c6a8b8b303f40bbb@russet.org.uk> (raw)
In-Reply-To: <E1kAPvH-00088K-8w@fencepost.gnu.org>

On 2020-08-25 04:46, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 
>   > > There are two Emacs modes for Rust already (rust-mode and
>   > > rustic). Neither are under GPL and both have a lot of 
> contributors, so
>   > > getting those into the Emacs distribution would be an uphill 
> struggle.
> 
>   > And rust-mode is on Melpa, so users can just install it via M-x
>   > list-packages, if they want to.
> 
> They can do that if they enable MELPA.  But we want to have a good
> Rust mode included in the Emacs core.


Well, there are already two rust modes (rust-mode and rustic) which have 
significant amounts of shared code, so that I've ended up fixing bugs in 
the two places. Having a third code base would be unfortunate. So, if 
you want this, I think find a way to get either rust-mode or rustic into 
core.

Phil





  reply	other threads:[~2020-08-25 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23  1:04 bug#42991: Rust support Alexander Summers
2020-08-23 21:30 ` phillip.lord
2020-08-24 13:04   ` Lars Ingebrigtsen
2020-08-25  3:46     ` Richard Stallman
2020-08-25 10:53       ` phillip.lord [this message]
2020-08-26  1:55         ` Richard Stallman
2020-08-24  3:21 ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bfc318aadfefaef1c6a8b8b303f40bbb@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=42991@debbugs.gnu.org \
    --cc=alexandermsummers@gmail.com \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.