Replace syntax highlighting styles in base.css to use SyntaxHighlighter instead of Pygments #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er instead of Pygments.
|
maybe you should push both now for ability to test, and then have a PR to remove the pygments after pygmentize is removed? :) |
|
I reckon that for the few people who need to test this, they can just pull down this branch while they're testing the changes to grunt-jquery-content ;) |
|
Landed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tracks along with this PR on grunt-jquery-content, which replaces Pygments with node-syntaxhighlighter. Once that issue has been merged, we'll need to pull in these CSS changes so the highlighted code blocks display properly.