From: "Robert P. Goldman" <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org babel does not work properly with included files
Date: Sun, 01 May 2011 20:52:40 -0500 [thread overview]
Message-ID: <da40bcf6-09f3-4ed2-822d-a2e5c04a2376@email.android.com> (raw)
In-Reply-To: <17693.1304299983@alphaville.americas.hpqcorp.net>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Also note that if you have an included file with MULTIPLE code blocks, this approach won't generalize....
Best,
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Nick Dokos <nicholas.dokos@hp.com> wrote:
Robert Goldman <rpgoldman@sift.info> wrote: foo.org: > * Purpose > > This document is intended to demonstrate that src buffer evaluation in > subsidiary, included files, does not work. > > * Demo > > #+include "~/src/org-test/bar.org" > > bar.org: > * Here's the demo > > #+begin_src sh :exports results :results output > echo "foo!" > #+end_src > As a workaround, try making the headings identical, i.e. bar.org looks like this: --8<---------------cut here---------------start------------->8--- * Demo #+begin_src sh :exports results :results output echo "foo!" #+end_src --8<---------------cut here---------------end--------------->8--- Nick
[-- Attachment #2: Type: text/html, Size: 1416 bytes --]
next prev parent reply other threads:[~2011-05-02 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 0:44 Org babel does not work properly with included files Robert Goldman
2011-05-02 1:33 ` Nick Dokos
2011-05-02 1:48 ` Robert P. Goldman
2011-05-02 3:43 ` Nick Dokos
2011-05-02 4:15 ` Robert P. Goldman
2011-05-02 1:52 ` Robert P. Goldman [this message]
2011-05-02 2:47 ` Robert Goldman
2011-05-05 16:56 ` Eric Schulte
2011-05-05 21:12 ` Robert Goldman
2011-05-05 21:27 ` Eric Schulte
2011-05-05 22:10 ` Robert Goldman
2011-05-11 14:24 ` Robert Goldman
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=da40bcf6-09f3-4ed2-822d-a2e5c04a2376@email.android.com \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).