From: Robert Goldman <rpgoldman@sift.info>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org babel does not work properly with included files
Date: Thu, 05 May 2011 17:10:51 -0500 [thread overview]
Message-ID: <4DC3206B.7050109@sift.info> (raw)
In-Reply-To: <87r58csurn.fsf@gmail.com>
On 5/5/11 May 5 -4:27 PM, Eric Schulte wrote:
>>>
>>> I'm not sure that the current behavior is a bug. Is it reasonable to
>>> place code block parameters into an included file? These parameters
>>> would not be successfully found during interactive evaluation, and could
>>> only plausibly be used during export as you anticipated.
>>
>> Aren't the code block parameters supposed to appear /with/ the code
>> block? So here's the use case:
>>
>> I have a file chapter.org. This contains a full draft of a chapter of
>> my manual. I finish it and circulate it for comments, then get it ready
>> for inclusion.
>>
>> Now I have manual.org and I want to include the main body of chapter.org
>> (typically there's some front matter I leave off).
>>
>> When I put the #include in manual.org, the source code snippets in
>> chapter.org, which used to work, no longer do.
>>
>> This doesn't seem like /such/ a crazy use case that it shouldn't work,
>> does it?
>>
>
> Oh, my apologies, apparently in scanning this email thread I
> mis-understood your use case.
>
> I've just tried to re-create the situation you've described above
> (including a file which contains code blocks). I was unable to
> reproduce your problem locally (the results of exporting both to html
> and tex are included). Could you modify the attached example
> sufficiently to demonstrate the problem you're experiencing?
I will work on it --- I have a somewhat complicated perl script that is
pulling stuff out for me and exporting results as source. Getting it to
work in a small example is tricky!
>
>>
>> [btw, I am not entirely sure I know what "header parameters" are ---
>
> see http://orgmode.org/manual/Header-arguments.html
That's what I thought --- I was just confused because the comment in the
code flips from using the term "argument" to "parameter," and I
considered the possibility that there were two different mechanisms.
Thanks,
r
next prev parent reply other threads:[~2011-05-05 22:10 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
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 [this message]
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=4DC3206B.7050109@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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).