unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: could matlab-mode be in ELPA or the GNU emacs tree (like auctex and org-mode)?
Date: Sun, 21 Nov 2021 10:22:26 +0200	[thread overview]
Message-ID: <837dd1syt9.fsf@gnu.org> (raw)
In-Reply-To: <87v90mrkvu.fsf@mat.ucm.es> (message from Uwe Brauer on Sun, 21 Nov 2021 09:08:37 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Sun, 21 Nov 2021 09:08:37 +0100
> 
> RMS if you read this: would you allow to have a part of matlab-mode that
> interacts with matlab via the so called matlab shell, to be part of ELPA or GNU
> emacs?
> 
> Rationale: there is already specific code that allows GNU emacs to be
> compiled in non free systems.

Can you explain in simple words what is so important about matlab-mode
that we'd like to have it in ELPA?  Is it syntax support, or is it the
fact that you can invoke the REPL of the Matlab interpreter from
Emacs, or is it something else?

I'm asking because I never understood why people who use Matlab would
like to use Emacs in conjunction with Matlab, since the Matlab
interactive mode provides so many features that are practically
necessary for any reasonable use of Matlab.  So what can Emacs
possibly add to that?



  parent reply	other threads:[~2021-11-21  8:22 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 [this message]
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
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=837dd1syt9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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).