From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Babel: How to call code in one org file into another org file
Date: Sat, 31 Oct 2015 10:57:17 +0100 [thread overview]
Message-ID: <87y4ej2wea.fsf@gmx.us> (raw)
In-Reply-To: CAFAhFSWrwyo7eAXk-Gp2Sb8BLkguTy+Rf-kRORg4kyYLhXD9EA@mail.gmail.com
Hi Lawrence,
Lawrence Bottorff <borgauf@gmail.com> writes:
> There are many, many Babel examples, but I can't seem to find this
> functionality: A function in a Lisp code block in one org file is to be
> called from a Lisp code block in another org file. Is this possible? I know
> you can stick stuff into your personal "Library of Babel," but I just want
> to write a Lisp block that calls a function from another org file. I'll
> have SLIME running, of course.
>
>
> file1.org:
> ...
>
> #+begin_src lisp
> (defun foo ()
> (...))
> #+end_src
>
> file2.org:
> ...
>
> #+begin_src lisp
> (defun baa ()
> (foo))
> #+end_src
At export time you could include a named block, but I’m not really sure
that gets you closer to what you want.
E.g. in file 1,
#+name: fun_foo
#+begin_src lisp
(defun foo ()
(...))
#+end_src
In file 2,
#+include: "file1.org::fun_foo"
#+begin_src lisp
(defun baa ()
(foo))
#+end_src
Rasmus
--
Spil noget med Slayer!
next prev parent reply other threads:[~2015-10-31 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 20:21 Babel: How to call code in one org file into another org file Lawrence Bottorff
2015-10-30 20:53 ` John Kitchin
2015-10-30 20:55 ` Thomas S. Dye
2015-10-30 22:57 ` briangpowell .
2015-10-31 0:14 ` Lawrence Bottorff
[not found] ` <m21tcbx2iy.fsf@andrew.cmu.edu>
2015-10-31 2:12 ` Lawrence Bottorff
2015-10-31 2:15 ` Lawrence Bottorff
2015-10-31 3:08 ` Thomas S. Dye
2015-10-31 3:58 ` Lawrence Bottorff
2015-10-31 15:41 ` Nick Dokos
2015-10-31 16:17 ` Lawrence Bottorff
2015-10-31 16:34 ` Nick Dokos
2015-10-31 16:51 ` Lawrence Bottorff
2015-11-02 7:09 ` Eric S Fraga
2015-11-02 13:36 ` Nick Dokos
2015-10-31 9:57 ` Rasmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-31 2:24 John Kitchin
2015-10-31 2:33 ` Lawrence Bottorff
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=87y4ej2wea.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).