From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jorgejavieran@yahoo.com.mx, emacs-devel@gnu.org
Subject: Re: are contributions on other programming languages than C and Emacs lisp bad idea?
Date: Sat, 21 Sep 2019 23:51:47 -0400 [thread overview]
Message-ID: <E1iBsuZ-0000m8-2G@fencepost.gnu.org> (raw)
In-Reply-To: <83d0ftqyy4.fsf@gnu.org> (message from Eli Zaretskii on Sat, 21 Sep 2019 21:36:03 +0300)
[[[ 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. ]]]
I think we should not include anything in the Emacs repository or
tarball that depends on Ada, Javascript, Rust, or anything other than
Emacs Lisp and C. The GNU Project sees no problem in writing in those
languages, but including that code in Emacs would make difficulties
for users.
In ELPA, if a package is useful only in conjunction with language Foo,
I think it is ok if building that package depends on language Foo.
--
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2019-09-22 3:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427040605.4453251.1569007946448.ref@mail.yahoo.com>
2019-09-20 19:32 ` are contributions on other programming languages than C and Emacs lisp bad idea? Jorge Araya Navarro
2019-09-20 21:11 ` Paul Eggert
2019-09-20 22:34 ` Stefan Monnier
2019-09-21 0:37 ` Jorge Javier Araya Navarro
2019-09-21 2:52 ` Devesh Sukhwal
2019-09-21 13:09 ` Stefan Monnier
2019-09-21 9:03 ` VanL
2019-09-21 9:46 ` Stephen Leake
2019-09-21 16:28 ` Jorge Javier Araya Navarro
2019-09-21 17:22 ` Ergus
2019-09-21 18:36 ` Eli Zaretskii
2019-09-21 21:29 ` Jorge Javier Araya Navarro
2019-09-22 15:01 ` Eli Zaretskii
2019-09-22 19:01 ` yyoncho
2019-09-22 3:51 ` Richard Stallman [this message]
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=E1iBsuZ-0000m8-2G@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jorgejavieran@yahoo.com.mx \
/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.