Pandoc template support

Requested by @EleanorKonik on the Discord’s #creative channel

Basically, you can write template files for most output formats which use a templating language to include bits of the input document. Using the Pandoc CLI the command will have a --template=file.tex if you’ve got a template called file.tex in the working directory or ~/.pandoc/templates.

My idea for the UX is to have a setting where you list files anywhere in your vault that you’d like to be templates (or specify a template directory?). Then, when you export, if there are any custom templates for that export type you should be prompted for the template you want, including the default one.

Related links:

• Official docs
• Default LaTeX template
• Simpler example

[gpl34]

What about having a template: in the YAML front matter. For example, saying:

---
template: local.latex
---

would be the same as --template=local.latex. That would allow to choose a different template per note. No need therefore to change the settings or to ask the user to choose a template each time one exports a note.

[Ellpeck]

@Ellpeck Do you have spaces in your absolute path to the template, that you wouldn’t have in your path to other metadata CLI options ?

As I said, the only time I tested this, I used a web URL (which is supported by the --template pandoc option, and also worked when i added it to the “additional arguments” section of the plugin settings), so no, no spaces!