The simple solution would be for templates to contain something like this````$for(filter-header-includes.<output_format>)$ $filter-header-includes.<output_format>$ $endfor$````with filter authors being trusted to make sure that the relevant variable is a MetaBlocks element where each child element is a RawBlock element of the appropriate format. This wouldn't require any code changes at all, just half an hour's work on the templates and some discipline on the part of filter authors./bpjDen 1 dec 2016 12:55 skrev "Kolen Cheung" <christi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:I was browsing some pandoc filters and see this comment:> pandoc-crossref uses metadata variable `header-includes` to add LaTeX definitions to output. However, Pandoc's command line option `--include-in-header`/`-H` overrides this variable. If you need to use `--include-in-header`, add pandoc-crossref-specific definitions as well. See [LaTeX customization](#latex-customization) for more information. I was thinking to use the `header-includes` in filters to put necessary "template" needed by the filter as well. But without the `-H` override the `header-includes` it won't be stable.It seems that at least there aren't specific reasons/situations when the current behavior is preferred (that `-H` override `header-includes` in YAML). May be we should make the change?--To view this discussion on the web visit https://groups.google.com/d/
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discus...@googlegroups.com .
To post to this group, send email to pandoc-...@googlegroups.com .msgid/pandoc-discuss/1902649a- .ac7f-4715-a80e-9d9c3659e025% 40googlegroups.com