Show where pygments can't parse code #1764
Open
Conversation
This file contains 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
Sometimes I make multiple edits to files and then when I try to `rake generate` my site I get a pygments parse error but I don't know where the file is. This will dump the code from the page that is causing the error to the stdout so the user can see which file is causing the problem and go into the file to find where the error is and repair it. I have scraped many websites using Jekyll because it's too cumbersome for me to back over many many posts looking for an error and moved back and forth to Wordpress because of this. Now that I know how to resolve this, I will no longer have to scrap whole posts and move from Markdown back to HTML. This will help future users too.
|
Solution comes from here: http://reckhhh.github.io/blog/2015/05/01/octopress-error-pygments-cant-parse-unknown-language/ |
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.
Sometimes I make multiple edits to files and then when I try to
rake generatemy site I get a pygments parse error but I don't know where the file is. This will dump the code from the page that is causing the error to the stdout so the user can see which file is causing the problem and go into the file to find where the error is and repair it. I have scraped many websites using Jekyll because it's too cumbersome for me to back over many many posts looking for an error and moved back and forth to Wordpress because of this. Now that I know how to resolve this, I will no longer have to scrap whole posts and move from Markdown back to HTML. This will help future users too.