From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: matlab-shell-run-command (was: workflow, matlab+latex in org file)
Date: Sun, 12 Mar 2017 15:24:10 +0000 [thread overview]
Message-ID: <87k27u34dh.fsf_-_@mat.ucm.es> (raw)
In-Reply-To: CAJ51ETqfKDyxVWvzbntuG2-5BERb=vkWUwjCCwPjVO-9PL3RFw@mail.gmail.com
>>> "John" == John Kitchin <jkitchin@andrew.cmu.edu> writes:
> You can put them into an elisp src block to try it out. They have to go in
> an init file to be permanent. I just made a symlink to the matlab
> executable on my path.
> The ipython functions are defined in ob-ipython,
> https://github.com/gregsexton/ob-ipython I think.
I just found out that it will not work for me since the matlab-kernel will
need the python support of matlab, which requires version 2016 o later.
And indeed the most annoying issue of executing matlab in an
org buffer using the babel interface was the fact that it was slow since
every time matlab needs to be restarted. Now that matlab-kernel thing
seems to resolve the issue. However it needs a very recent version of
matlab.
Therefore my proposal:
there exists already a matlab-shell written in
lisp written by Eric Ludlam and others which does not require a restart
of matlab for every call.
Couldn't your code (defun org-babel-execute:matlab (body params) trying
to use matlab-shell-run-command or matlab-shell-run-region?
I don't understand enough of either function to try to modify it.
Regards
Uwe
next prev parent reply other threads:[~2017-03-12 15:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 12:32 workflow, matlab+latex in org file Uwe Brauer
2016-07-11 14:05 ` John Kitchin
2016-07-11 14:11 ` Uwe Brauer
2016-07-11 15:55 ` John Kitchin
2016-07-11 16:12 ` Uwe Brauer
2017-03-10 16:08 ` Uwe Brauer
2017-03-10 17:51 ` Scott Randby
2017-03-10 21:15 ` Uwe Brauer
2017-03-10 21:56 ` John Kitchin
2017-03-10 22:50 ` Uwe Brauer
2017-03-10 23:17 ` SOLVED (was: workflow, matlab+latex in org file) Uwe Brauer
2017-03-11 23:50 ` workflow, matlab+latex in org file Scott Randby
[not found] ` <5e1e71e3698e415ca51a0b9e3cab5dac@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 18:03 ` Eric S Fraga
2017-03-10 21:18 ` Uwe Brauer
2017-03-11 8:04 ` Uwe Brauer
2017-03-11 13:23 ` John Kitchin
2017-03-11 14:16 ` Uwe Brauer
2017-03-11 14:22 ` John Kitchin
2017-03-11 14:54 ` Uwe Brauer
2017-03-11 16:50 ` Uwe Brauer
2017-03-11 16:53 ` John Kitchin
2017-03-12 15:24 ` Uwe Brauer [this message]
2017-10-20 11:03 ` Uwe Brauer
2017-10-20 11:54 ` Uwe Brauer
[not found] ` <cf7ef1dfa1cf455bbaf63ab5fbdf18e5@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-11 10:37 ` Eric S Fraga
2017-03-11 14:12 ` Uwe Brauer
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k27u34dh.fsf_-_@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@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/org-mode.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).