emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: running a source code by name
Date: Mon, 28 May 2018 18:58:54 -0400	[thread overview]
Message-ID: <87a7sje6a9.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: xgzd0xgf31x.fsf@hafogvatn.is

"Julian M. Burgos" <julian.burgos@hafogvatn.is> writes:

> Dear list,
>
> I have an org file with an R source code block.  I want to have a second
> code block with an elisp call to run that first code.  Something like this
>
>
> #+begin_src emacs-lisp :results silent :tangle no
>
> ... Some elisp code to run the "myRcode" block.

(org-sbe myRcode)

Untested.

>
> #+end_src
>
> #+NAME: myRcode
> #+beg in_src R :results silent :tangle no
>
> ... My R code here
>
> #+end_src
>
> What would be the best way to do it?
>
> Many thanks,
>
> Julian
>
>
> --
> Julian Mariano Burgos, PhD
> Hafrannsóknastofnun, rannsókna- og ráðgjafarstofnun hafs og vatna/
> Marine and Freshwater Research Institute
> Botnsjávarsviðs / Demersal Division
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax:  +354-5752001
> Netfang/Email: julian.burgos@hafogvatn.is
>
>

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

      parent reply	other threads:[~2018-05-28 22:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 11:13 running a source code by name Julian M. Burgos
2018-05-28 14:35 ` Eric S Fraga
2018-05-28 16:25   ` Berry, Charles
2018-05-28 20:16     ` John Kitchin
2018-05-28 20:30       ` Berry, Charles
2018-05-30  6:59         ` Julian M. Burgos
2018-05-30 16:16           ` Berry, Charles
2018-05-28 22:58 ` Nick Dokos [this message]

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=87a7sje6a9.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).