On 2023-06-03, at 10:37, Ihor Radchenko <yanta...@posteo.net> wrote:
> Marcin Borkowski <mb...@mbork.pl> writes: > >>> You can loop over links in the exported subtree and export any extra if >>> necessary. For example, in the `org-export-filter-parse-tree-functions'. >> >> Interesting. The main problem with it is that the docstring is rather >> concise and I don't understand it well enough to use it. > > Org export passes the actual parsed and filtered AST that will be > exported to `org-export-filter-parse-tree-functions'. You can modify and > traverse the parse tree as you need. Yeah, that I do understand. Problem is, I don't know how the AST is structured, what functions operate on it etc. I am aware that I could learn all of that from the source and experimenting, but it would probably be a bit time-consuming, and other ways turned out to be much easier (which means better for me – I want something simple). As an aside, inspecting deeply nested structures in Elisp seems a pain in the neck. Does anyone know a good method of interactively inspecting them? My usual approach (Edebug) is next to useless when the value displayed in the minibuffer is a deeply nested list with dozens or hundreds of elements at different levels... TIA, -- Marcin Borkowski http://mbork.pl
