From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: could matlab-mode be in ELPA or the GNU emacs tree (like auctex and org-mode)?
Date: Mon, 22 Nov 2021 08:56:34 +0100 [thread overview]
Message-ID: <87r1b8y66l.fsf@mat.ucm.es> (raw)
In-Reply-To: E1moz5v-000415-9O@fencepost.gnu.org
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
>>> "RS" == Richard Stallman <rms@gnu.org> writes:
> [[[ 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 know that matlab is a commercial product and its license is not
>> compatible with the GPL, but the same could be said about MS Windows OS
>> and MacOS and yet GNU Emacs support these OSs.
> The GNU Project has standard about what to do in situations like this.
> Its conclusion in this case is that it is ok to include Matlab mode in
> Emacs. Likewise, ok to make Emacs run on Windows or MacOS.
Ok, thanks for the clarification RMS.
Anybody else: is this settled, then?
I am asking because I have to start round two of code-digging as Stefan suggested to find out whether each and every line that has been included by patches a long time ago is
1. either deleted or
2. in case it survived try to contact the author.
That is a rather time consuming activity and I don't want in the last minute to hear an objection to include matlab-mode, as you maybe understand.
Regards
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-11-22 7:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 17:53 could matlab-mode be in ELPA or the GNU emacs tree (like auctex and org-mode)? Uwe Brauer
2021-11-20 22:42 ` Philip Kaludercic
2021-11-21 0:00 ` Stefan Monnier
2021-11-21 8:08 ` Uwe Brauer
2021-11-21 8:17 ` Po Lu
2021-11-21 8:25 ` Uwe Brauer
2021-11-21 9:23 ` Po Lu
2021-11-21 9:34 ` Uwe Brauer
2021-11-21 9:55 ` Po Lu
2021-11-21 10:04 ` Uwe Brauer
2021-11-21 11:40 ` dick
2021-11-21 20:16 ` Andy Moreton
2021-11-21 10:58 ` Alfred M. Szmidt
2021-11-21 12:16 ` dick
2021-11-21 14:17 ` Uwe Brauer
2021-11-21 16:15 ` Alfred M. Szmidt
2021-11-21 16:25 ` Uwe Brauer
2021-11-21 16:39 ` Alfred M. Szmidt
2021-11-21 17:13 ` Uwe Brauer
2021-11-21 14:49 ` Stefan Monnier
2021-11-21 16:31 ` Uwe Brauer
2021-11-21 17:32 ` dick
2021-11-22 13:58 ` Stefan Monnier
2021-11-23 6:13 ` Richard Stallman
2021-11-21 8:22 ` Eli Zaretskii
2021-11-21 8:32 ` Uwe Brauer
2021-11-21 8:39 ` Eli Zaretskii
2021-11-21 8:51 ` Uwe Brauer
2021-11-21 9:05 ` Eli Zaretskii
2021-11-21 9:29 ` Uwe Brauer
2021-11-21 11:32 ` dick
2021-11-21 14:26 ` Uwe Brauer
2021-11-22 2:30 ` Richard Stallman
2021-11-22 7:56 ` Uwe Brauer [this message]
2021-11-22 13:59 ` Stefan Monnier
2022-02-14 11:51 ` Jean Louis
2022-02-14 11:49 ` Jean Louis
2022-02-16 4:11 ` 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
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=87r1b8y66l.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@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 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).