Hello,
Mark Edgington writes:
> I am providing a minimal example that still exhibits the problem for me (on
> the latest git rev):
>
> --- BEGIN EXAMPLE ---
> * Heading 1 :ignore:
> ** Heading 2 :export:
> *** Heading 3 :ignore:
Nicolas Goaziou nicolasgoaziou.fr> writes:
> No, it isn't. However I could only reproduce it with empty footnote
> definitions.
>
> In any case, this is now fixed. Thank you.
I am providing a minimal example that still exhibits the problem for me (on
the latest git rev):
--- BEGIN EXAM
Hello,
Mark Edgington writes:
> I have noticed, however, that even if I have (setq
> org-export-with-broken-links 't), I am still unable to export a
> narrowed buffer that contains a footnote reference ("Definition not
> found for footnote..."). Is this behavior intentional?
No, it isn't. Howe
The org-export-with-broken-links option was introduced in order to
allow exports to proceed when a link isn't able to be resolved.
Sometimes this happens when trying to export a narrowed region of a
buffer.
I have noticed, however, that even if I have (setq
org-export-with-broken-links 't), I am s
