From: Eric Schulte <schulte.eric@gmail.com>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BABEL] the julia language
Date: Sun, 03 Mar 2013 12:05:51 -0700 [thread overview]
Message-ID: <87bob0mhgw.fsf@gmail.com> (raw)
In-Reply-To: <CAFiLVrYZi_A_atOKv6fshpVf+RPP=8RE611nLBvtT_2gpUKQhg@mail.gmail.com> (Jay Kerns's message of "Sun, 3 Mar 2013 07:53:49 -0500")
Hi Jay,
Having read through intro-julia.org and scanned ob-julia.el I have to
say this looks great. Thanks for sharing!
Would you be willing to contribute ob-julia.el to the Org-mode
repository? I don't see you listed as an Org-mode contributor (see
[1]), so to do so you would likely have to complete the FSF copyright
attribution. Please let me (and more importantly Bastien) know if this
is something you'd like to do, so we can help get julia support into
Org-mode.
Additionally, it would be nice for your excellent introduction to be
added to worg, and for julia to be listed as a supported babel language
(see [2]).
Cheers,
Jay Kerns <gjkernsysu@gmail.com> writes:
> Hello,
>
> Maybe you've heard about the relatively new language, "julia" [1]?
> The ESS team added support for it some months back [2] and they've
> been working on it more recently even [3]. It seemed natural to
> investigate Babel support for julia and after quite a bit of fiddling
> with ob-R.el I believe I've sorted out the major pieces:
>
> git://github.com/gjkerns/ob-julia.git
>
> There's an "ob-julia.el" file which is the meat, then
> "ob-julia-doc.org" and "ob-julia-beamer.org" files for testing, plus
> an "intro-julia.org" file in case you're new to julia and would like
> to learn more. For testing you'd need a recent installation of julia
> [2] and you'd need an almost bleeding-edge version of ESS [4]. By the
> way, it was written under the development branch of Org so if you
> haven't updated recently you might need that too.
>
> LaTeX/HTML/Beamer export is working, C-c C-c evaluation of code
> chunks, plotting figures (need the Winston package), etc. Session
> evaluation is required at least for the time being.
>
> If you see ways to improve it I'd appreciate any feedback.
>
> Cheers,
> Jay
>
> [1] http://julialang.org/
> [2] https://stat.ethz.ch/pipermail/ess-help/2012-September/008212.html
> [3] https://stat.ethz.ch/pipermail/ess-help/2013-February/008640.html
> [4] https://github.com/emacs-ess/ESS
Footnotes:
[1] http://orgmode.org/worg/org-contribute.html
[2] http://orgmode.org/worg/org-contrib/babel/languages.html
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-03-03 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 12:53 [BABEL] the julia language Jay Kerns
2013-03-03 19:05 ` Eric Schulte [this message]
2013-03-03 22:27 ` Jay Kerns
2013-03-04 1:58 ` Evan Misshula
2013-03-04 13:36 ` Eric Schulte
2013-03-04 17:53 ` Bastien
2013-03-04 18:12 ` Jay Kerns
2013-03-04 19:39 ` Bastien
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=87bob0mhgw.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gjkernsysu@gmail.com \
/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).