Re: [O] how to handle backend-specific types as fuzzy link targets during export

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Hello, Eric Schulte schulte.e...@gmail.com writes: Attached OK, now I get it. You're working at the wrong level. `latex-fragment' is an object (inline) type, but you're inserting it at the element's level. The equivalent (non inline)

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Hello, Eric Schulte schulte.e...@gmail.com writes: A related question. Is there a command to re-number figures in export? Figures are not numbered in the parse tree: their number is computed on the fly during export, with `org-export-get-ordinal'. After adding latex-environments in a

[O] how to handle backend-specific types as fuzzy link targets during export

Hello, In the function `org-export-resolve-fuzzy-link' at line 4078 of ox.el the `org-element-all-elements' variable is used to map over all elements in the parse tree when looking for a possible link target. However some trees hold valid backend-specific types which are not members of the

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Hello, Eric Schulte schulte.e...@gmail.com writes: In the function `org-export-resolve-fuzzy-link' at line 4078 of ox.el the `org-element-all-elements' variable is used to map over all elements in the parse tree when looking for a possible link target. However some trees hold valid

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Hello, Eric Schulte schulte.e...@gmail.com writes: In the function `org-export-resolve-fuzzy-link' at line 4078 of ox.el the `org-element-all-elements' variable is used to map over all elements in the parse tree when looking for a possible

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Eric Schulte schulte.e...@gmail.com writes: Sure. I have added a function to org-export-filter-parse-tree-functions which replaces a custom keyword with either a latex-fragment or an HTML link wrapped in a paragraph depending on the export backend. The latex fragment basically has the

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Eric Schulte schulte.e...@gmail.com writes: Sure. I have added a function to org-export-filter-parse-tree-functions which replaces a custom keyword with either a latex-fragment or an HTML link wrapped in a paragraph depending on the export

Re: [O] how to handle backend-specific types as fuzzy link targets during export

Hello, Eric Schulte schulte.e...@gmail.com writes: Attached OK, now I get it. You're working at the wrong level. `latex-fragment' is an object (inline) type, but you're inserting it at the element's level. The equivalent (non inline) element is `latex-environment', which is, for example: