Charles Berry <ccbe...@ucsd.edu> writes: Thanks for the tips. I did not see a way to do the advice here. For what I need, we need to save parameters for each code block. But it appears they are all affected by one function org-babel-exp-process-buffer, and advising this kind of function is tantamount to rewriting the function!
my solution is here: http://kitchingroup.cheme.cmu.edu/blog/2014/09/22/Showing-what-data-went-into-a-code-block-on-export/ I agree it would be nice if that was unnecessary, but it is not too terrible for now. > John Kitchin <jkitchin <at> andrew.cmu.edu> writes: > >> >> I did some more digging on the missing :parameters during export, and it >> seems that the src block itself is different during export than in the >> buffer. Below illustrates what I mean. In the buffer, if I look at the >> contents of the code block using output from org-element-at-point, it >> looks as I expect, with the complete header. But, using the same method >> in the export, it is clear that the header args are not there. >> >> I have not figured out where they disappear yet. >> > [snip] > > Instrument org-export-as. Then step thru it. > > Before this line: > > (org-export-execute-babel-code) > > the buffer copy ( my-buffer<2>, say ) will show the parameters/headers. > > After that line is executed, they are gone. > > You can work around this by `advicing' various babel functions and inserting > things you want to save as attributes, but it would be nice not to need > to do that. > > HTH, > > Chuck > > > > > -- ----------------------------------- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
