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

Kramdown support with options / extensions and coderay #239

Merged
3 commits merged into from Nov 23, 2010

Conversation

Projects
None yet
2 participants
@jasongraham
Contributor

jasongraham commented Nov 21, 2010

I've added kramdown support, including support for the use of kramdown's options sent to the kramdown HTML converter specified in _config.yaml, as well as corresponding tests.

The last commit allows you to customize the parameters passed from kramdown to coderay, should it be wanted (coderay is not required to use kramdown, I use python pygments myself). I'm not sure if you'd want to keep this commit, but I felt that since I had already implemented the other option parameters, I should do them all.

Lastly, I'm a n00b when it comes to ruby, so suggestions on improving the tests or option passing are welcome.

jasongraham added some commits Oct 21, 2010

Add support for kramdown HTML converter options
  http://kramdown.rubyforge.org/converter/html.html#options

  Example: In the _config.yaml,

  markdown: kramdown

  kramdown:
    auto_ids: true
Add kramdown's support for coderay
  - no test added so that coderay isn't added to list of developer
    dependencies

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.