>> >> 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?
example.tar.bz2
Description: Binary data
> > [btw, I am not entirely sure I know what "header parameters" are --- see http://orgmode.org/manual/Header-arguments.html > > are these the parameters that come from the #+begin_src line? If so, > shouldn't they definitely be read from the #+begin_src line? They > can't very well be read from manual.org, which doesn't contain the > #+begin_src line.] > These could appear with the code block, or as a property in an enclosing heading. Another example of a case where the original file is needed rather than the exported file would be the case of exporting a subtree which includes a block which references a variable defined elsewhere in the file. > > Sorry if I wasn't clear in my original message. > No problem, I believe I misread this email thread. Thanks -- Eric > > Best, > r > -- Eric Schulte http://cs.unm.edu/~eschulte/
