Oxygene language detection #460
Merged
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
…do we need this, other languages don't specify one)
…tension (which Delphi also has) fixes the build fail
|
guess not :( |
…per Oxygene lexer in pigments.rb
|
This is failing because there is no detected Pygments lexer for Oxygene. Investigating. |
|
Ah, I see — pygments/pygments.rb#71. Our general policy is to hold off until pygments upstream has reviewed and merged the patch. I'll leave this issue open and will merge once upstream has it. |
|
@tnm It seems that pygments.rb hasn't had any activity for over a month; I'm also waiting on a pull request there so that I may submit one for linguist. Is there some way we can work around this issue so we can get our stuff into linguist (and thus supported on GitHub) faster? |
|
+1 on what hoelzro said. anything we can do here? |
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.
trying a new pull request after updating to latest master. Hopefully that solves the odd test failures, who knows...