From: "Julian M. Burgos" <julian.burgos@hafogvatn.is>
To: "Berry, Charles" <ccberry@ucsd.edu>
Cc: Eric S Fraga <esflists@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: running a source code by name
Date: Wed, 30 May 2018 06:59:24 +0000 [thread overview]
Message-ID: <xgzmuwhr5mb.fsf@hafogvatn.is> (raw)
In-Reply-To: <790089EC-9901-4115-9F0C-7B9F0A913B0A@ucsd.edu>
Thanks guys. A combination of org-babel-goto-named-src-block and
org-babel-execute-src-block did the trick.
I am building an org template to create html presentations using the R
package xaringan. In my case each slide is a markdown source block.
The elisp block tangles everything into a Rmd file, and the R block runs
rmarkdown::render and opens the resulting html file in a browser.
Thanks again. :)
Berry, Charles writes:
> OK, I have to note that this will also do the job that the OP requested:
>
> #+begin_src emacs-lisp :results silent :var result=myRcode
>
> #+end_src
>
> although it seems a little strange to write an empty src block for its side effects.
>
> I suppose I should have suggested this in the first place:
>
> #+begin_src emacs-lisp :results silent :noweb yes
> <<myRcode()>>
> #+end_src
>
> although the return value from the noweb reference could be troublesome depending on what else is included in the latter src block.
>
> Chuck
>
>> On May 28, 2018, at 1:16 PM, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>>
>> Here is yet another variation, that may be suitable for what you want:
>>
>>
>> #+name: myPyCode
>> #+BEGIN_SRC python
>> print('Hello')
>> #+END_SRC
>>
>>
>> #+BEGIN_SRC emacs-lisp :var results=myPyCode
>> results
>> #+END_SRC
>>
>> #+RESULTS:
>> : Hello
>>
>>
>> John
>>
>> -----------------------------------
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> @johnkitchin
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkitchingroup.cheme.cmu.edu&data=02%7C01%7C%7Cfdaa27b411604ed32a0108d5c4d9fa01%7C8e105b94435e4303a61063620dbe162b%7C0%7C0%7C636631362846470731&sdata=4K%2B96NBf5KPaoz13laaAR0%2FaqY2FlefTLy%2BPXy6YtO8%3D&reserved=0
>>
>>
>> On Mon, May 28, 2018 at 9:25 AM, Berry, Charles <ccberry@ucsd.edu> wrote:
>>
>>
>> > On May 28, 2018, at 7:35 AM, Eric S Fraga <esflists@gmail.com> wrote:
>> >
>> > On Monday, 28 May 2018 at 11:13, Julian M. Burgos wrote:
>> >> 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.
>> >
>> > Something along the lines of:
>> >
>> > (org-babel-goto-named-src-block "myRcode")
>> > (org-babel-execute-src-block)
>> >
>> > should do the job?
>>
>> Maybe wrap it in
>>
>> (save-excursion ... )
>>
>> or use
>>
>> (org-sbe "myRcode")
>>
>> or
>>
>> (org-babel-ref-resolve "myRcode")
>>
>> which both can also pass :var args.
>>
>> HTH,
>>
>> Chuck
>>
>>
>>
>>
>>
--
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
next prev parent reply other threads:[~2018-05-30 7:00 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 [this message]
2018-05-30 16:16 ` Berry, Charles
2018-05-28 22:58 ` Nick Dokos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xgzmuwhr5mb.fsf@hafogvatn.is \
--to=julian.burgos@hafogvatn.is \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=jkitchin@andrew.cmu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.