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

Possibility of passing configs to Literate.markdown via Remark.slideshow #54

Closed
wants to merge 2 commits into from

Conversation

ekobir
Copy link

@ekobir ekobir commented Nov 27, 2022

Added kwargs to pass configs to Literate.markdown from Remark.slideshow call.

@@ -4,17 +4,17 @@ authors = ["Pietro Vertechi"]
version = "0.3.2"

[deps]
BinaryProvider = "b99e7846-7c00-51b0-8f62-c81ae34c0232"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a change from #53, so it shouldn't be in this PR. Same for many of the changes below.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed that is the case. Will close this PR.

@@ -24,7 +24,7 @@ const depfiles = joinpath.(_pkg_assets, depnames)
const style_css = joinpath(_pkg_assets, "style.css")

function slideshow(presentation_dir;
title="Title", documenter=true, options=Dict())
title="Title", documenter=true, options=Dict(), kwargs...)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confess I'm not too keen on forwarding all keywords indiscriminately to Literate. Could we require the user to pass a config dict here instead? Maybe it can just be an additional literate_options=Dict() keyword argument?

This should also be documented in the README.

@ekobir ekobir closed this Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants