[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] how to handle backend-specific types as fuzzy link targets during ex
From: |
Eric Schulte |
Subject: |
[O] how to handle backend-specific types as fuzzy link targets during export |
Date: |
Tue, 24 Jun 2014 06:59:53 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
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
`org-element-all-elements' variable (e.g., `latex-fragment'). This
results in named targets not being resolved during export.
I'm currently working around this locally by let-binding
`org-element-all-elements' in line 1967 of ox-latex.el, but I imagine
there should be a more general solution.
Thoughts?
Thanks,
Eric
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
- [O] how to handle backend-specific types as fuzzy link targets during export,
Eric Schulte <=
- 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/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