Skip to content
This repository was archived by the owner on Sep 11, 2021. It is now read-only.

Changed pygments: true by highligher: pygments. #10

Merged
merged 1 commit into from
May 26, 2014
Merged

Changed pygments: true by highligher: pygments. #10

merged 1 commit into from
May 26, 2014

Conversation

ggtools
Copy link

@ggtools ggtools commented May 25, 2014

On startup with jekyll 2.0.3, the following message is displayed:

Deprecation: The 'pygments' configuration option has been renamed to 'highlighter'. Please update your config file accordingly. The allowed values are 'rouge', 'pygments' or null.

@dbtek
Copy link
Owner

dbtek commented May 26, 2014

Hey Christophe,

Thanks for informing. I checked on jekyll docs by Github. There is still pygments setting there. I guess gh-pages currently supports it. Did you test it on gh-pages?

Thanks.

@ggtools
Copy link
Author

ggtools commented May 26, 2014

Hi,

There's currently no actual issue by keeping pygments: true instead of highlighter: pygments just a warning when jekyll parses the site. It should definitely work on gh pages.The only thing you cannot do with the old syntax is to use rouge to highlight your code instead of pygments.

Cheers

@dbtek
Copy link
Owner

dbtek commented May 26, 2014

I guess we are cool to use the new syntax on gh-pages, just the documentation needs to be updated. Thanks for contribution!

dbtek added a commit that referenced this pull request May 26, 2014
Changed pygments: true by highligher: pygments.
@dbtek dbtek merged commit 187ae4a into dbtek:master May 26, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants