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
Hello,
John Kitchin jkitc...@andrew.cmu.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
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Thanks for the clarification. Is there any chance you know why this
transformation is done? Does it avoid some problem?
Hello,
John Kitchin jkitc...@andrew.cmu.edu writes:
Thanks for the tips. I did not see a way to do the advice here. For what
Hello,
John Kitchin jkitc...@andrew.cmu.edu writes:
Thanks for the clarification. Is there any chance you know why this
transformation is done? Does it avoid some problem?
No idea.
Regards,
--
Nicolas Goaziou
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
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
Hi John,
Look at the functions ‘org-babel-exp-src-block’ which calls
‘org-babel-exp-do-export’, which calls ‘org-babel-exp-code’. The tl;dr
version is that indeed the babel export machinery does change the code
block in substantial ways, including the removal of parts of it.
This plays merry
