-
Notifications
You must be signed in to change notification settings - Fork 938
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 / Rouge not working for Code Syntax Highlighting #20
Comments
Hi CodeRedPaul, I'm in the same boat, I can't use 'Rouge'. I use jekyll v3.7.3, rouge v2.2.1, jekyll-theme-prologue v0.3.2 on Ubuntu |
Did you add a stylesheet? While Jekyll comes with built-in Rouge support, it does not come with a pre-defined stylesheet so coloring won't work out of the box. You can find various example stylesheets online, or you can use a tool* like pygments-css to generate one. Stick that stylesheet in the *Correction: |
@Drakmyth I'm not that familiar with Jekyll, do you mind helping me out a bit? Say I want to use |
Yep, either location works. It just changes the path you pass into the import statement. In my setup, I have (for example) |
* Add syntax highlighting Related: chrisbobbe/jekyll-theme-prologue#20 http://richleland.github.io/pygments-css/ github-linguist/linguist#1984 * Add unlicense header for highlight colors
I was having the problem where Rogue didn't seem to do anything at all (not wrapping code keywords in Then I discovered jekyll/jekyll#3641 (comment), removed kramdown:
syntax_highlighter: rouge |
* Add syntax highlighting Related: chrisbobbe/jekyll-theme-prologue#20 http://richleland.github.io/pygments-css/ github-linguist/linguist#1984 * Add unlicense header for highlight colors
* Add syntax highlighting Related: chrisbobbe/jekyll-theme-prologue#20 http://richleland.github.io/pygments-css/ github-linguist/linguist#1984 * Add unlicense header for highlight colors
Hi Chris
Having an issue getting Rouge to work properly with your theme. I've tried a couple of things... My latest attempt below as per this GitHub issue:
Any ideas?
Thanks so much,
Paul
The text was updated successfully, but these errors were encountered: