[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export
From: |
Nicolas Goaziou |
Subject: |
Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export |
Date: |
Tue, 23 Sep 2014 23:10:14 +0200 |
Hello,
Jacob Gerlach <address@hidden> writes:
> While I expect that there's no code overlap with macro expansion, I asked
> about similar "stop on unresolved content" behavior with respect to links
> here: http://article.gmane.org/gmane.emacs.orgmode/90010/
>
> That discussion died off so I thought I'd bring up the topic again here.
>
> Would it be possible to cause export to stop (configurably, as discussed)
> when a link can't be resolved instead of just applying a special format
> (i.e. org-latex-link-with-unknown-path-format)
I have no objection to return an error when a fuzzy link, and id link or
a custom id link cannot be matched.
However, I do not like the idea of configurability as it would make the
code a bit more complex for little gain.
Regards,
--
Nicolas Goaziou
- [O] [RFC] [PATCH] Warn about unexpanded macros on export, Aaron Ecay, 2014/09/19
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Nicolas Goaziou, 2014/09/23
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Aaron Ecay, 2014/09/27
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Nicolas Goaziou, 2014/09/28
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Rasmus, 2014/09/23
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Aaron Ecay, 2014/09/28
- Re: [O] [RFC] [PATCH] Warn about unexpanded macros on export, Nicolas Goaziou, 2014/09/28