-
Notifications
You must be signed in to change notification settings - Fork 10
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
Extensions with underscores not parsing correctly #10
Comments
This is because that isn't the correct way to pass an extension to Pandoc. The actual invocation would be pandoc --from markdown+markdown_in_html_blocks rather than pandoc --from markdown --markdown_in_html_blocks So it seems all extensions would be handled incorrectly here. |
Similar issue: I'm trying to remove the implicit_figures extension. I'd imagine this should work:
But I'm getting My guess is that @radixdiaboli is right, and the underscores are being converted to hyphens, which is causing pandoc to try and subtract the extension called "implicit" as well as the extension called "figures". |
@dawaltconley : I was struggling with a similar problem. Not sure if works in all cases, but in your case, the problem can be solved by taking advantage of the fact that the underscore appears in the option VALUE, not in the option name. So that should be:
With this, there will be no conversion of underscores in the value. |
I think I have experienced the same bug. Pandoc extensions like smart are working, but I cannot get the table_captions extension to work. Anyone have any suggestions for a (temporary at least) solution? |
It seems that's not the case anymore:
But the issue seems to come from the underlying pandoc wrapper gem jekyll-pandoc/lib/jekyll-pandoc.rb Line 17 in 9143c20
|
I'm trying to use the 'markdown_in_html_blocks' extension. When I add it in _config,yml and try to build with Jekyll, I get the following error:
Notice that the error shows the option as having hyphens instead of underscores. I tested this out with a few other extensions that have underscores and saw the same pattern. Random extensions that do not have underscores did not result in an error.
_config.yml:
The text was updated successfully, but these errors were encountered: