unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: kixtart-mode
Date: Sat, 12 Nov 2022 23:18:26 -0500	[thread overview]
Message-ID: <E1ou4Ru-0004qg-4r@fencepost.gnu.org> (raw)
In-Reply-To: <jwvleoju1pt.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 09 Nov 2022 18:58:19 -0500)

[[[ 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 is no dependency or inter-op with the interpreter, and the package
  > > was developed independently - since the source code is not available it
  > > is also impossible for me to create any link to it.

  > Yes, I understand this.  The question is rather one of policy/strategy
  > than one of copyright.

That is true.

  > > But if this is the final decision I'll live with it.

  > I can never remember exactly what is the policy in such cases, so I'm
  > hoping Richard will chime in.

Our general policy makes a subtle distinction between these two cases:

1. If a nonfree program FOO is not well known, we don't even mention that
it exists.  Because we don't want to promote using FOO.

2. If a nonfree program FOO is well known and widely used, something to
help and encourage FOO's users to use some GNU packages along with FOO
is good.

3. Anything that would encourage the existing users of some GNU packages
to use FOO with them is bad.

Is SickStart the main scripting language for Windows now?  If so, it
will surely be widely used, so case 2 would apply.  Then we would want
to include support for editing it.

BUT, it is a bad thing if people use SickStart to write scripts
that they could have written in a free scripting language.
Is there anything we can do to urge people to use Perl or Python
or Bash instead of SickStart?

Why would someone, on Windows, use SickStart rather than those other
scripting packages?  Does it have some major advantage, for use on
Windows?

Or is it that Microsoft is going to tell everyone that "SickStart is
the scripting language for Windows!  Be the first on your block to try
SickStart!" and people will be led by the nose?

Maybe we can come up with a way to encourage people to choose some
free and portable scripting language, even when using Windows.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2022-11-13  4:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 20:55 [ELPA] New package: kixtart-mode morgan
2022-11-09 21:10 ` Philip Kaludercic
2022-11-09 21:24   ` Morgan Willcock
2022-11-09 22:04 ` Stefan Monnier
2022-11-09 22:48   ` Morgan Willcock
2022-11-09 23:58     ` Stefan Monnier
2022-11-10  0:20       ` Morgan Willcock
2022-11-10  0:40         ` Juanma Barranquero
2022-11-13  4:18       ` Richard Stallman [this message]
2022-11-13  7:09         ` Eli Zaretskii
2022-12-11 23:33           ` Richard Stallman
2022-12-12 12:14             ` Eli Zaretskii
2022-12-11 23:50           ` Óscar Fuentes
2022-12-12  6:17             ` North Year
2022-12-12 12:21             ` Eli Zaretskii
2022-12-12 14:00               ` Óscar Fuentes
2022-12-20 23:59                 ` Morgan Willcock
2022-11-10  8:16   ` Akib Azmain Turja
2022-11-10  8:25     ` Eli Zaretskii
2022-11-10  9:00       ` Akib Azmain Turja

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=E1ou4Ru-0004qg-4r@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).