Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Req] YAML for --latex-engine #1780

Closed
ghost opened this issue Dec 1, 2014 · 4 comments
Closed

[Feature Req] YAML for --latex-engine #1780

ghost opened this issue Dec 1, 2014 · 4 comments

Comments

@ghost
Copy link

ghost commented Dec 1, 2014

Hi, as part of converting a document from markdown to pdf eg.

pandoc source.md -o pdf.pdf

we need to add --latex-engine=lualatex for instance to get lualatex

Can we have a YAML metadata for the same thing, like it is with other commands


---
title: title
latex-engine: lualatex
...
@ghost ghost changed the title YAML for --latex-engine [Feature Req] YAML for --latex-engine Dec 1, 2014
@mpickering
Copy link
Collaborator

This sort of thing has been suggested lots in the past but there is an unresolved issue. Currently no information apart from the document AST is passed back from the reader to the main program which makes it impossible to affect further execution in this way.

@ghost
Copy link
Author

ghost commented Dec 2, 2014

Okay thanks for the reply. And sorry, I searched through the last 3-4 pages and could find similar but not exact. Apologies for the replica.

On Tue, Dec 2, 2014 at 10:07 AM, Matthew Pickering
notifications@github.com wrote:

This sort of thing has been suggested lots in the past but there is an unresolved issue. Currently no information apart from the document AST is passed back from the reader to the main program which makes it impossible to affect further execution in this way.

Reply to this email directly or view it on GitHub:
#1780 (comment)

@ghost
Copy link

ghost commented Mar 4, 2015

Would a dotfile in the current directory work?

@mb21
Copy link
Collaborator

mb21 commented May 5, 2018

Closing in favour of #4627

@mb21 mb21 closed this as completed May 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants