[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] how to handle backend-specific types as fuzzy link targets durin
From: |
Nicolas Goaziou |
Subject: |
Re: [O] how to handle backend-specific types as fuzzy link targets during export |
Date: |
Tue, 24 Jun 2014 13:56:28 +0200 |
Hello,
Eric Schulte <address@hidden> 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 backend-specific types which are not members of the
> `org-element-all-elements' variable (e.g., `latex-fragment'). This
> results in named targets not being resolved during export.
I do not understand what you are trying to achieve. Line 4078 tries to
find elements with a #+NAME affiliated keyword in the parse tree. LaTeX
fragments cannot have such keywords.
Maybe an example would help.
Regards,
--
Nicolas Goaziou
- [O] how to handle backend-specific types as fuzzy link targets during export, Eric Schulte, 2014/06/24
- Re: [O] how to handle backend-specific types as fuzzy link targets during export,
Nicolas Goaziou <=
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Eric Schulte, 2014/06/24
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Nicolas Goaziou, 2014/06/24
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Eric Schulte, 2014/06/24
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Nicolas Goaziou, 2014/06/24
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Eric Schulte, 2014/06/30
- Re: [O] how to handle backend-specific types as fuzzy link targets during export, Nicolas Goaziou, 2014/06/30