Thibault Marin writes:
> OK, then it looks like I may be able to build a list of source block
> name/tangle filename pairs on pre-processing, store it in a global
> variable and use it when processing source-blocks. It is probably a
> little hack-ish but that would be fine for me. On my initial
Thanks for your reply, it is very helpful.
Nicolas Goaziou writes:
> They are not. You may want to see how cache is used with info in, e.g.,
> `org-export-get-footnote-definition'.
That looks like what I was trying to achieve (except better), thanks.
> The buffer used during export is unlikely
Hello,
Thibault Marin writes:
> *Question 1*: Is the `org-element-src-block-parser' function supposed to
> resolve
> the tangle filename (including inheritance, i.e. to handle the 3 :tangle
> sources listed above)?
No, it isn't.
> From the docstring, it would appear
Hi all,
I am following up on a question I posted here a while ago to show my progress in
case it can help others and to ask for a few clarifications. I would appreciate
any feedback.
My goal is to add a label to source blocks on HTML export to indicate the name
of the file to which the block
Hi list,
I have an org file that I am tangling into multiple files, and exporting
to html. What I would like to do is to label each source block in the
exported html with the filename used for tangling this specific block.
I don't have a strong opinion about the actual appearance of the label