From: Richard Stallman <rms@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: emacs-26 3fc05cf: Scripts to automate windows binary distribution
Date: Wed, 25 Oct 2017 23:42:43 -0400 [thread overview]
Message-ID: <E1e7Z47-0006Ty-Vc@fencepost.gnu.org> (raw)
In-Reply-To: <87r2trg01m.fsf@gmx.de> (message from Michael Albinus on Wed, 25 Oct 2017 09:27:01 +0200)
[[[ 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. ]]]
> Likely I've missed the discussion, but do we want to distribute Python
> scripts with Emacs?
I see no reason to stubbornly reject them.
All else being equal, it would be better to stick to the languages we
use now. (Using more languages would mean more than people need to learn.)
But if there is a substantial benefit from using Python, we can.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
prev parent reply other threads:[~2017-10-26 3:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171024173456.23065.52677@vcs0.savannah.gnu.org>
[not found] ` <20171024173457.C45BE2031F@vcs0.savannah.gnu.org>
2017-10-25 7:27 ` emacs-26 3fc05cf: Scripts to automate windows binary distribution Michael Albinus
2017-10-25 8:37 ` Phillip Lord
2017-10-25 10:16 ` Michael Albinus
2017-10-25 10:53 ` Kaushal Modi
2017-10-25 11:06 ` Michael Albinus
2017-10-25 14:44 ` Eli Zaretskii
2017-10-25 14:59 ` Michael Albinus
2017-10-25 15:08 ` Óscar Fuentes
2017-10-25 15:19 ` Eli Zaretskii
2017-10-25 15:27 ` Michael Albinus
2017-10-25 11:03 ` Noam Postavsky
2017-10-25 15:42 ` Phillip Lord
2017-10-25 12:11 ` Stefan Monnier
2017-10-25 15:45 ` Phillip Lord
2017-10-26 3:42 ` 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
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=E1e7Z47-0006Ty-Vc@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=phillip.lord@russet.org.uk \
/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).