Another try for fixing ">" comparison for Octopress#2
Open
bdillahu wants to merge 1 commit intobelkadan:masterfrom
Open
Another try for fixing ">" comparison for Octopress#2bdillahu wants to merge 1 commit intobelkadan:masterfrom
bdillahu wants to merge 1 commit intobelkadan:masterfrom
Conversation
Fixing usage with Octopress where ">" comparison doesn't work. Based on info from https://github.com/soonhokong pull request
Owner
|
I don't understand why |
Author
|
I'm afraid answering the "why > doesn't work" is beyond me at the moment. I understand the issue that this probably isn't the best fix, but wanted to offer it up in case it was some help. Thanks for all your work on this fork! |
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
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.
Fixing usage with Octopress where ">" comparison doesn't work. Based on info from https://github.com/soonhokong pull request
I'm not a great Ruby person, so this may still have issues, but it seems like its been working for me.
You do have to be careful if you're changing layouts or something to actually touch the index files that are affected.