-
Notifications
You must be signed in to change notification settings - Fork 13
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
Why aren't all pandoc command line options supported #14
Comments
To add to this: I don't know how codebraid works, but could it be used as a pandoc filter? That way codebraid wouldn't have to deal with pandoc options at all. |
I'll look into adding support for the new Codebraid sends a document through Pandoc multiple times. It uses Pandoc to convert a document into AST form, then replaces code with raw output in the AST, then uses Pandoc to convert the AST back to Markdown, and finally uses Pandoc to convert this output Markdown to the final format. This guarantees that when Codebraid executes code to generate Markdown text, that Markdown text will be interpreted by Pandoc within the full context of the document. Running separate Pandoc processes on generated Markdown snippets would be simpler, but it would lose context information (for example, references wouldn't work in some cases). All user-supplied Pandoc options are only guaranteed to be used the final time that Pandoc runs. Some options must be added/removed in the intermediate steps to make everything work correctly. |
I understand. Would be great if this could be added, but no need to hurry. In the meantime, would using |
Using |
Ok. What exactly do you mean with markdown to markdown producing the original document with code replaced by output? What about setex vs atx style headers? When I thought about using a json temporary file my concern was not so much performance but rather such options where one choice could lead to a lossy transfoelation. |
Ah... transformation |
Running something like |
I've added support for Currently, there is a limitation that the input format, output format, and output file must be given on the command line when using |
I have just tried converting a document using the relatively new
-d
option, which resulted in codebraid throwing errors... Why? Aren't pandoc arguments just passed through?The text was updated successfully, but these errors were encountered: