emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: "Robert P. Goldman" <rpgoldman@sift.info>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Org babel does not work properly with included files
Date: Sun, 01 May 2011 23:43:08 -0400	[thread overview]
Message-ID: <4419.1304307788@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Your message of "Sun, 01 May 2011 20:48:58 CDT." <90a049ce-df0a-41ca-9a5e-617953d20e54@email.android.com>

Robert P. Goldman <rpgoldman@sift.info> wrote:


> Sorry, I think I have created a red herring here by leaving that code blo=
> ck in both files. To see what the problem really is, consider the case wh=
> ere the source code block appears ONLY in the included file.
> 
> (I tested the source block in the master file to make sure it worked befo=
> re I copied it into the included file and forgot to remove it from the ma=
> ster file.)
> 

??

There was no code block in foo.org: just the include.

Only bar.org had the code block.

As for multiple code blocks in the included file (your next message),
yeah, probably. But my suggestion was just a (possible) workaround:
it's definitely not a fix.

Nick

  reply	other threads:[~2011-05-02  3:43 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 [this message]
2011-05-02  4:15       ` Robert P. Goldman
2011-05-02  1:52   ` Robert P. Goldman
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=4419.1304307788@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \
    /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).